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.

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

Consider making Gameplay screens in templates / demos ephemeral. #891

Open
bryanedds opened this issue Nov 5, 2024 · 1 comment
Open
Labels
discussion todo issue related to testing or other tertiary tasks

Comments

@bryanedds
Copy link
Owner

From discord -

bryanedds — Today at 9:49 AM
so, if we wanted to removed the additional state handling when the gameplay screen is not selected, we could have the engine transition from some screen to none then on transition out finish, have it create the gameplay screen on the fly and transition to it.
this should already be doable by all the APIs
we'd just have to set up the templates a bit differently (and update the demos to match)
the non-gameplay screens would continue to be globally persistent tho as only the gameplay screen would get this special treatment

@bryanedds bryanedds added discussion todo issue related to testing or other tertiary tasks labels Nov 5, 2024
@bryanedds
Copy link
Owner Author

I don't know if I really like this idea overall because it's really nice to be able to set the state of the screen while it's not selected, such as in the EditModes override. Tho, I suppose an alternative is to set state on non-gameplay screen and have the gameplay screen read from that upon creation... but I dunno. That's kinda ug too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion todo issue related to testing or other tertiary tasks
Projects
None yet
Development

No branches or pull requests

1 participant