diff --git a/README.md b/README.md index 74866e8..25d3b2d 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,7 @@ For proxies the recommended setup is to create one game object per screen and pe * **Transition Url (url)** - Optional URL to call when the screen is about to be shown/hidden. Use this to trigger a transition (see the section on [transitions](#transitions)). * **Focus Url (url)** - Optional URL to call when the screen gains or loses focus (see the section on [screen focus](#screen-focus-gainloss)). -![](docs/setup.png) +![](docs/setup_proxy.png) ### Collection factories For factories the recommended setup is to create one game object per screen and per game object attach a collection factory component and an instance of the ```screen_factory.script``` provided by Monarch. The ```screen_factory.script``` will take care of the setup of the screen. All you need to do is to make sure that the script properties on the script are correct: @@ -46,6 +46,8 @@ For factories the recommended setup is to create one game object per screen and * **Transition Id (url)** - Optional id of the game object to send a message to when the screen is about to be shown/hidden. Use this to trigger a transition (see the section on [transitions](#transitions)). * **Focus Id (url)** - Optional id of the game object to send a message to when the screen gains or loses focus (see the section on [screen focus](#screen-focus-gainloss)). +![](docs/setup_factory.png) + ## 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: diff --git a/docs/setup_factory.png b/docs/setup_factory.png new file mode 100644 index 0000000..7328b98 Binary files /dev/null and b/docs/setup_factory.png differ diff --git a/docs/setup_proxy.png b/docs/setup_proxy.png new file mode 100644 index 0000000..885e8ea Binary files /dev/null and b/docs/setup_proxy.png differ