You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some cases where a number of systems should be turned on and off as a group. For example, when an in-game menu is open, and we want to pause the physics, sprite animations, player input, and timers, but we don't want to pause the menu system or the renderer.
Currently I have logic at the beginning of every system I want to pause that essentially looks like:
I could see a downside to this feature: later when systems aren't running because they're paused it wouldn't be clear immediately that it's part of a paused set. With the explicit return in each system, it's a lot more clear. Whether a system is paused or not would be in the system declaration code, which might be in another file/location.
There are some cases where a number of systems should be turned on and off as a group. For example, when an in-game menu is open, and we want to pause the physics, sprite animations, player input, and timers, but we don't want to pause the menu system or the renderer.
Currently I have logic at the beginning of every system I want to pause that essentially looks like:
But this is kind of ugly. It might be nice to offer a way to register systems as part of a set, and pause/resume that set.
The text was updated successfully, but these errors were encountered: