Skip to content

Conversation

@atlv24
Copy link
Contributor

@atlv24 atlv24 commented Jan 16, 2026

Objective

  • Show how to drive loop for rendering externally.

Solution

  • Add example.

Testing

Produces:
{EFA87DC0-0054-4EB4-8863-9DE13CC492D5}

Copy link
Contributor

@TimJentzsch TimJentzsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool and useful example, though as someone who isn't deep into this topic, some more explanatory comments would be very helpful!

@kfc35 kfc35 added A-Rendering Drawing game state to the screen C-Examples An addition or correction to our examples D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Needs-Review Needs reviewer attention (from anyone!) to move forward labels Jan 16, 2026
Copy link
Member

@tychedelia tychedelia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree re: more comments. Also, I think it might be helpful to call this externally_driven_headless_renderer? That might be too verbose, but there is some conceptual overlap with externally driven event looping (a la https://docs.rs/winit/latest/winit/platform/pump_events/trait.EventLoopExtPumpEvents.html). It's worth making clear that "external" here means no windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Rendering Drawing game state to the screen C-Examples An addition or correction to our examples D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Needs-Review Needs reviewer attention (from anyone!) to move forward

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

4 participants