order for storyboard callbacks willEnterScene and didExitScene has changed?

aisaksen · November 14, 2012, 4:22pm

It seems like the order that willEnterScene and didExitScene gets called has recently changed. Has anyone else noticed this? This change happened in the last month or so.

it used to be like this for Scene A and B

A.willEnterScene
A.enterScene
A.exitScene
A.didExitScene
B.willEnterScene
B.enterScene
B.exitScene
B.didExitScene

but now it seems like its

A.willEnterScene
A.enterScene
A.exitScene
B.willEnterScene
A.didExitScene
B.enterScene
B.exitScene
B.didExitScene

This introduces a lot of bugs in my code which assumed the other way. Is this intentional new behavior? [import]uid: 122310 topic_id: 33002 reply_id: 333002[/import]

aisaksen · November 14, 2012, 4:27pm

I’m using version 926 of Enterprise which has the old behavior, and i noticed the new behavior in the latest build 968. So somewhere between those builds, this switched around…and its causing chaos on my game which assumed the former behavior. [import]uid: 122310 topic_id: 33002 reply_id: 131001[/import]

Danny · November 14, 2012, 5:03pm

Hi asiaksen,

Thanks for reporting this. I will look into this for you asap. [import]uid: 84637 topic_id: 33002 reply_id: 131008[/import]

aisaksen · November 14, 2012, 4:27pm

I’m using version 926 of Enterprise which has the old behavior, and i noticed the new behavior in the latest build 968. So somewhere between those builds, this switched around…and its causing chaos on my game which assumed the former behavior. [import]uid: 122310 topic_id: 33002 reply_id: 131001[/import]

Danny · November 14, 2012, 5:03pm

Hi asiaksen,

Thanks for reporting this. I will look into this for you asap. [import]uid: 84637 topic_id: 33002 reply_id: 131008[/import]

roaminggamer · November 16, 2012, 11:13am

@aisaksen,

Nice catch. [import]uid: 110228 topic_id: 33002 reply_id: 131271[/import]

Danny · November 16, 2012, 11:43am

Hey aisaksen.

We are still trying to ascertain which daily build this occurred in. Needless to say we will have a fix out for this in one of the upcoming daily builds asap.

Thank you for reporting it and for your patience. [import]uid: 84637 topic_id: 33002 reply_id: 131277[/import]

roaminggamer · November 16, 2012, 11:13am

@aisaksen,

Nice catch. [import]uid: 110228 topic_id: 33002 reply_id: 131271[/import]

Danny · November 16, 2012, 11:43am

Hey aisaksen.

We are still trying to ascertain which daily build this occurred in. Needless to say we will have a fix out for this in one of the upcoming daily builds asap.

Thank you for reporting it and for your patience. [import]uid: 84637 topic_id: 33002 reply_id: 131277[/import]

bpran · November 20, 2012, 3:04am

Is this bug fixed in the latest public release (2012.971)? [import]uid: 31508 topic_id: 33002 reply_id: 131729[/import]

walter · November 20, 2012, 11:39am

yes, it is unfortunately in the public release. [import]uid: 26 topic_id: 33002 reply_id: 131807[/import]

bpran · November 20, 2012, 3:04am

Is this bug fixed in the latest public release (2012.971)? [import]uid: 31508 topic_id: 33002 reply_id: 131729[/import]

walter · November 20, 2012, 11:39am

yes, it is unfortunately in the public release. [import]uid: 26 topic_id: 33002 reply_id: 131807[/import]

Danny · November 23, 2012, 7:17am

Update:

This issue has been fixed (from my testing it has existed from way back to the last public release (v894) and maybe earlier)

The fix will be available once daily builds kick off again.

Thanks again for your patience and for reporting this issue [import]uid: 84637 topic_id: 33002 reply_id: 132174[/import]

aisaksen · November 23, 2012, 7:23am

Thanks for the update, Danny, and glad to hear its fixed now…definitely looking forward to updating to a more recent build before doing our Android release. (Its definitely not broken in Build 926 which is what I used to release my game.) [import]uid: 122310 topic_id: 33002 reply_id: 132176[/import]

Danny · November 23, 2012, 7:31am

Hey aisaksen.

Unless the storyboard version in v926 in corona enterprise differed from the one used in the standard version of corona.

I tested on the normal version of corona on 926 (and 894) and got the same incorrect scene event order as you described.

If you didn’t, would you mind emailing me a simple test case that shows otherwise? my email is danny [at] coronalabs.com

Thanks again. [import]uid: 84637 topic_id: 33002 reply_id: 132178[/import]

aisaksen · November 24, 2012, 7:08am

I will email you the test case now. Its basically just the default App that corona builds, with some prints added, and willEnterScene and didExitScene added to both views. It does the correct behavior in Corona Simulator on 926 (not just enterprise). [import]uid: 122310 topic_id: 33002 reply_id: 132238[/import]

EHO · November 24, 2012, 10:03am

What is the intended sequencing of the scene events? This is something I’ve been wondering about for some time.

Is it meant to work as the following once the bug is fixed?:

A.willEnterScene
A.enterScene
A.exitScene
A.didExitScene
B.willEnterScene
B.enterScene
B.exitScene
B.didExitScene [import]uid: 105707 topic_id: 33002 reply_id: 132251[/import]

Danny · November 23, 2012, 7:17am

Update:

This issue has been fixed (from my testing it has existed from way back to the last public release (v894) and maybe earlier)

The fix will be available once daily builds kick off again.

Thanks again for your patience and for reporting this issue [import]uid: 84637 topic_id: 33002 reply_id: 132174[/import]

aisaksen · November 23, 2012, 7:23am

Thanks for the update, Danny, and glad to hear its fixed now…definitely looking forward to updating to a more recent build before doing our Android release. (Its definitely not broken in Build 926 which is what I used to release my game.) [import]uid: 122310 topic_id: 33002 reply_id: 132176[/import]