Great, so there are some definite numbers on the table :-) Seems like the Activity approach is 20 times slower. Then again, most users won't probably notice the 40-90ms.
the 40 ms in your example contain creating a new GestureDetector (which you don't do when you switch within your activity), and packing and retrieving the start value into an intent extra. Packing and retrieving the extra gives the application additional value (because your activity may communicate with 3rd party activities), so to be fair, you could drop that and simply pass your long through a static long. Could save another 10ms? Peli On Oct 27, 3:22 pm, "Robert K." <[EMAIL PROTECTED]> wrote: > Here's the side-by-side app I > wrote:http://www.anddev.org/viewtopic.php?p=12247#12247 > > setContentView(view) needed 2-5 ms, new Activity approach 40-90ms for > this simple example. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
