Gui issue using Monarch transitions

ItsPixel · June 25, 2019, 8:42pm

Hi guys!
I am started to use monarch for switching scenes and it worked fine until I tried to add transitions.
After adding transition url, gui is started to act kinda weird.
It stops to redirect to the correct scene and gui is not removed as expected.

To switch scenes I use proxy collection with monarch.show(hash(“start”))
Code of transition is very simple:

function on_message(self, message_id, message, sender)
	print("GUI transition - message_id: " .. message_id)
	pprint(message)
	if message_id == hash("transition_show_in") then 
		msg.post(sender, monarch.TRANSITION.DONE)
	end
end

Cannot find where is the problem, can somebody advice something?

britzl · June 26, 2019, 3:04am

Hi. So the transition isn’t actually doing anything? I’m guessing that since it is instantaneous that this messes with monarch. You can try to add a timer before sending the transition done message just to verify.

ItsPixel · June 26, 2019, 7:07pm

Does not help, will continue to investigate.

britzl · June 26, 2019, 8:34pm

I can take a look if you can share a zip with a repro case. Preferably in a GitHub issue or here.

ItsPixel · June 27, 2019, 6:47pm

Well I have found that there is missing monarch_screen_transition_out_finished.
Not sure why, but it does not send done message.

Proccess looks like this:

monarch.show(‘start’) //preloaded
DEBUG:SCRIPT: Transition: [transition_show_in]
DEBUG:SCRIPT: Transition: [transition_done]
monarch.show(‘next_scene’)
DEBUG:SCRIPT: Transition: [transition_show_out]
// should be transition_done, but missing it
DEBUG:SCRIPT: Transition: [transition_show_in]
DEBUG:SCRIPT: Transition: [transition_done]

Defined transitions:

function init(self)
	self.transition = transitions.create(gui.get_node("box"))
	.show_in(transitions.fade_out, gui.EASING_LINEAR, 2)
	.show_out(transitions.fade_in, gui.EASING_LINEAR, 2)
end

function on_message(self, message_id, message, sender)
	self.transition.handle(message_id, message, sender)
end

Seems it does not wait till transition finishes and moves to the next transition.

britzl · June 27, 2019, 9:22pm

Ok. Can you create a minimal repro case and share it with me?

ItsPixel · June 28, 2019, 10:32pm

Uploaded: https://bitbucket.org/seqq86/monarch/src/master

britzl · June 29, 2019, 1:33pm

Ok, so I took a look at your project. Some comments:

You have two screens, level1 and start.
Both screens use the same transition url /gui#transitions
The transition logic at /gui#transitions defines a transition for show_out and show_in
When you click you alternate between showing level1 and start

The problem is that when you show one screen it triggers the show_in transition and at the same time you hide the other screen which triggers the show_out transition. This means that the transition logic in /gui#transitions gets invoked twice and at the same time. Only one of these will finish.

The solution is to have the transition handler set up per screen. Meaning that level1 has one transition url and start has another. This way they won’t conflict like they do today.

ItsPixel · June 29, 2019, 2:05pm

Thank you for your time. But what if I plan to have 70+ scenes? If there is possibility to run transitions in sequance?

britzl · June 29, 2019, 3:38pm

You could create a transition instance per screen at runtime:

local transitions = require "monarch.transitions.gui"
local monarch = require "monarch.monarch"

local function get_transition(self, screen)
	if not self.transitions[screen] then
		self.transitions[screen] = transitions.create(some_node)
			.show_in(transitions.fade_in, gui.EASING_OUTQUAD, 0.6, 0)
			.show_out(transitions.fade_out, gui.EASING_INQUAD, 0.6, 0)
	end
	return self.transitions[screen]
end

function init(self)
	self.transitions = {}
end

function on_message(self, message_id, message, sender)
	if message_id == monarch.TRANSITION.SHOW_IN or message_id == monarch.TRANSITION.SHOW_OUT then
		local transition = get_transition(self, message.screen)
		transition.handle(message_id, message, sender)
	end
end

ItsPixel · June 29, 2019, 5:28pm

Thank you for your answers!

ItsPixel · June 30, 2019, 6:03pm

Well… pretty strange transition_show_in does not sends screen in message.

britzl · June 30, 2019, 7:52pm

Hmm, it should. What does message contain?

And used here:

github.com/britzl/monarch

monarch/monarch.lua

master


      
          
          local function preload(screen)
          	log("preload() preloading screen", screen.id)
          	assert(screen.co, "You must assign a coroutine to the screen")
          
          	if screen.preloaded then
          		log("preload() screen already preloaded", screen.id)
          		return true
          	end
          
          	screen.preloading = true
          	if screen.proxy then
          		log("preload() proxy")
          		if M.has_missing_resources(screen.id) then
          			local error_message = ("preload() collection proxy %s is missing resources"):format(tostring(screen.id))
          			log(error_message)
          			screen.preloading = false
          			return false, error_message
          		end
          		screen.wait_for = WAITFOR_PROXY_LOADED
          		msg.post(screen.proxy, MSG_ASYNC_LOAD)

And here:

github.com/britzl/monarch

monarch/monarch.lua

master


      
          		if collectionfactory.get_status(screen.factory) == collectionfactory.STATUS_UNLOADED then
          			collectionfactory.load(screen.factory, function(self, url, result)
          				assert(coroutine.resume(screen.co))
          			end)
          			coroutine.yield()
          			if screen.unregistered then
          				return false, "Screen was unregistered while loading"
          			end
          		end
          
          		if collectionfactory.get_status(screen.factory) ~= collectionfactory.STATUS_LOADED then
          			local error_message = ("preload() error while loading factory resources for screen %s"):format(tostring(screen.id))
          			log(error_message)
          			screen.preloading = false
          			return false, error_message
          		end
          	end
          	log("preload() preloading done", screen.id)
          	screen.preloaded = true
          	screen.preloading = false
          	return true

hungle · September 12, 2019, 5:50am

I’m having the same issue that you described.

I have one scene and when I reload it (while that scene is loaded), the fade out transition does not work but only the fade in transition work.

Can you suggest any simple solution for this?

britzl · September 12, 2019, 5:57am

I would need to know more about the problem. Can you please create a ticket and also share a repro case so that I can test and see if it’s possible to create a fix:

hungle · September 12, 2019, 6:31am

Created the ticket and provided the repro case!

britzl · September 12, 2019, 6:44am

Thank you. I will take a look later.