Expose more of the game loop internals to the user #119
Labels
Area: API/Ergonomics
Issues relating to the crate's API and how it feels to use
Area: Game Loop
Issues relating to the main game loop.
Type: Feature Request
Improvements that could be made to the code/documentation.
It'd be nice if it were possible for users to opt out of the standard game loop and write their own, if they so desire.
Most of the groundwork for this is already there - the missing bits are:
The implementation of the actual looping needs to provided by Tetra, so that we can abstract over blocking/non-blocking APIs. I think this will probably boil down to the user providing a closure that represents one iteration of the game loop, and then scheduling that closure will be handled by the engine.
The text was updated successfully, but these errors were encountered: