After a first compilation of my AIR for IOS app with AIR 2.7 the situation was not good.
The application that was developed and optimized for AIR 2.6 was not smooth at all 🙁
A few tests later, I isolated the problem: The setTimout() method does not work properly (?) in AIR 2.7 for IOS.
I solved the problem by coding a small static class to manage multiple timeout using an unique enterFrame event.
Thx to Seraf for bug fix and clear(id) method 🙂
Timeout.create(myMethod, 300, "optional param");
Below are screenshots of the setTimeout() VS my Timeout.execute() test on my iPhone 3GS.
Below the test for FP 10.1.
Note that my class performs better or equal to the setTimeout() method (Win7 – FF4 – FP 11).