3
0
mirror of https://github.com/britzl/monarch.git synced 2025-06-27 10:27:49 +02:00

Added note on nested screens

Fixes #35
This commit is contained in:
Björn Ritzl 2019-01-10 10:18:03 +01:00 committed by GitHub
parent 753d003861
commit 2fa4b59041
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -48,6 +48,10 @@ For factories the recommended setup is to create one game object per screen and
![](docs/setup_factory.png) ![](docs/setup_factory.png)
Note: Monarch supports dynamic collection factories (ie where the "Load Dynamically" checkbox is checked).
## Nesting screens
Sometimes it might be desirable to have a screen that contains one or more sub-screens or children, for instance popups that are used only by that screen. Monarch supports nested screens only when the parent screen is created via a collection factory. If the parent screen is loaded via a collection proxy the sub/child-screens won't be able to receive any input.
## Navigating between screens ## Navigating between screens
The navigation in Monarch is based around a stack of screens. When a screen is shown it is pushed to the top of the stack. When going back to a previous screen the topmost screen on the stack is removed. Example: The navigation in Monarch is based around a stack of screens. When a screen is shown it is pushed to the top of the stack. When going back to a previous screen the topmost screen on the stack is removed. Example: