Monarch did not stack the first screen (SOLVED)

Huy_Nguyen · April 7, 2022, 3:11am

Hi, I’m having a problem with Monarch, specifically is the stacking system. I’ve follow the doc, looking at the example, but for some reasons when I try to call the screen for the first time, it did not stack, so am I doing anything wrong, or it’s a bug?

The screen is there, but somehow the stacking system did not work. I’m using Defold version 1.3.0 and did not update yet.

Thank you!

WhiteBoxDev · April 7, 2022, 5:33am

The monarch.show() function you called just before print(monarch.get_stack()) incorporates coroutines according to the source: https://github.com/britzl/monarch/blob/master/monarch/monarch.lua

Monarch takes a frame or two to load a new screen. Therefore, your monarch.get_stack() function won’t show anything until at least a frame later. For example, try printing its contents in your script’s update() function. You’ll notice that the stack now shows your screen.

Huy_Nguyen · April 7, 2022, 6:02am

Oh I see it now, but I also find another problem: when I use use monarch.show() to show other screen, it did not stack the second screen and instead, it unload the first screen and in the stack there is only second screen.

I want to stack the “in_game” screen on top of the “level_selected” screen so that I can go back using the monarch.back() function.

Can you help me with this issue please?

Thank you!!!

britzl · April 7, 2022, 6:08am

Correct. And if you have transitions it can take even longer. The fourth argument to monarch.show() is a callback function which will be called when the screen is fully visible:

github.com/britzl/monarch

README_API.md

master


# Monarch API

## monarch.show(screen_id, [options], [data], [callback])
Show a Monarch screen. Note that the screen must be registered before it can be shown. The `init()` function of the screen script (either `screen_proxy.script` or `screen_factory.script`) takes care of registration. This operation will be added to the queue if Monarch is busy.

**PARAMETERS**
* `screen_id` (string|hash) - Id of the screen to show.
* `options` (table) - Options when showing the new screen (see below).
* `data` (table) - Optional data to associate with the screen.  Retrieve using `monarch.data()`.
* `callback` (function) - Optional function to call when the new screen is visible.

The options table can contain the following fields:

* `clear` (boolean) - If the `clear` flag is set Monarch will search the stack for the screen that is to be shown. If the screen already exists in the stack and the clear flag is set Monarch will remove all screens between the current top and the screen in question.
* `reload` (boolean) - If the `reload` flag is set Monarch will reload the collection proxy if it's already loaded (this can happen if the previous screen was a popup).
* `no_stack` (boolean) - If the `no_stack` flag is set Monarch will load the screen without adding it to the screen stack.
* `sequential` (boolean) - If the `sequential` flag is set Monarch will start loading the screen only after the previous screen finished transitioning out.
* `pop` (number) - If `pop` is set to a number, Monarch will pop that number of screens from the stack before adding the new one.

This file has been truncated. show original

That’s strange. I’m not sure what’s going on there to be honest. Do you have any errors in your console? You can get additional information about what Monarch is doing by enabling extra logging using monarch.debug():

github.com/britzl/monarch

README_API.md

master


# Monarch API

## monarch.show(screen_id, [options], [data], [callback])
Show a Monarch screen. Note that the screen must be registered before it can be shown. The `init()` function of the screen script (either `screen_proxy.script` or `screen_factory.script`) takes care of registration. This operation will be added to the queue if Monarch is busy.

**PARAMETERS**
* `screen_id` (string|hash) - Id of the screen to show.
* `options` (table) - Options when showing the new screen (see below).
* `data` (table) - Optional data to associate with the screen.  Retrieve using `monarch.data()`.
* `callback` (function) - Optional function to call when the new screen is visible.

The options table can contain the following fields:

* `clear` (boolean) - If the `clear` flag is set Monarch will search the stack for the screen that is to be shown. If the screen already exists in the stack and the clear flag is set Monarch will remove all screens between the current top and the screen in question.
* `reload` (boolean) - If the `reload` flag is set Monarch will reload the collection proxy if it's already loaded (this can happen if the previous screen was a popup).
* `no_stack` (boolean) - If the `no_stack` flag is set Monarch will load the screen without adding it to the screen stack.
* `sequential` (boolean) - If the `sequential` flag is set Monarch will start loading the screen only after the previous screen finished transitioning out.
* `pop` (number) - If `pop` is set to a number, Monarch will pop that number of screens from the stack before adding the new one.

This file has been truncated. show original

If you are unable to figure out what is wrong then please open a ticket on GitHub and attach a small project where this problem happens.

Huy_Nguyen · April 7, 2022, 6:41am

I just used the monarch.debug() but I’m not so sure what I’m looking at or how to read the debug console, but here it is:

This is the process of me transition from the “level” screen to “in_game” screen. Do you have any idea of what the issue is? Is it because of the version of defold version of I’m using? (It’s 1.3.0) Or is it might be other issues?

Thank you!!!

britzl · April 7, 2022, 6:55am

No, the version of Defold has nothing to do with this. Could you please create a support ticket here: Sign in to GitHub · GitHub

Please include a zip file with a small sample project where I can test this.

Huy_Nguyen · April 7, 2022, 10:54am

Loopformer.zip (2.6 MB)
This is the file contain the game, and I’ve created, and yes, I’ve post the issue that I’ve facing with on github. Can you check it out? And I want to apologize in advance as the code and the structure is kind of messy and spaghetti , but I really want to find the solution to fix this issue. Thank you so much!!!

britzl · April 7, 2022, 11:54am

I took a quick look and you have set your “level” (the level select) screen as a popup. You can’t stack other screens on top of a popup (unless it is another popup and you have the “Popup on Popup” checkbox toggled).

Uncheck the “Popup” checkbox on that screen and you’re good!

Huy_Nguyen · April 7, 2022, 12:53pm

OMG I WANT TO SAY THANK YOU SO SOOO MUCH!!!
Welp, it’s kinda dumb of me but only this issue has driven me nut whole day already, and yet the solution to the problem is soooooooo simple. I’ve been smiling and laughing for 30 minutes already
Anw, thank you so much and wish you have a great day