Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Screen / state management #37

Closed
ryanisaacg opened this issue Jan 19, 2018 · 0 comments
Closed

Screen / state management #37

ryanisaacg opened this issue Jan 19, 2018 · 0 comments

Comments

@ryanisaacg
Copy link
Owner

Because the game_loop macro require all control flow through a single struct and its associated functions, there should be some convenient mechanism to embed multiple screens / states within the struct.
leod pushed a commit to leod/quicksilver that referenced this issue Jun 3, 2023
@ryanisaacg
Added a Screen trait and a macro to use Screens to drive the game loop (
fcc0fcd 
ryanisaacg#42)

* Added a Screen trait and a macro to use Screens to drive the game loop

* Created an InitialScreen trait that the first screen must implement

Resolves ryanisaacg#37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ryanisaacg