Hi Remi
There was a bug in my code. Got it working. - Sorry about that.
One more thing: *emy.goBack()* and *window.history.back()* - Can I use
either one?
regards
Rune
2014-06-05 15:57 GMT+03:00 Remi Grumeau :
> Nope, no easy build-in solution. Just like with native apps, you have to
> do y
Nope, no easy build-in solution. Just like with native apps, you have to do
your homework :)
By the way, you have events to help you with that.
http://www.emy-library.org/documentation/1.0/core-documentation.html#event-custom
beforetransition / aftertransition
Those events are triggered each time
Hi Remi
No good Remi. 70%?!! - I was hoping for better news :((
So you go from screen A to B and to C. At C you update some information
which means you also need to update screen A and B. So after the update you
go straight to screen B and before doing so you update the screen and
everything's ok
eh eh :)
If you don't play the rules, be ready to face those kind of problems ;)
Emy deals with going from screen A to screen B by itself. If you want no
transitions between screens, just set emy.transitionMode to "none"
http://www.emy-library.org/documentation/1.0/core-documentation.html#emy-tra
