Always use *emy.goBack()* !!
That's VERY important
Remi
On Fri, Jun 6, 2014 at 8:22 AM, Rune Back rune.b...@gmail.com wrote:
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?
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
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
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
Hi
I've got all pages in one *section/section*. When changing to another
page I change the content of this *section/section* This raises the
need of changing the backButton so that it instead of doing something like
*window.history.back()* it might call *myFunction(myVar)* where I can
update the
Hi
How do I make the backButton do a pop (i.e. history.go(-1);) insted of a
push like now?
Rune
--
You received this message because you are subscribed to the Google Groups
iPhoneWebDev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
