On Fri, May 18, 2012 at 1:40 AM, Simon Giddings <[email protected]>wrote:
> To TreKing : I quite clearly explained that the drawing area was where I > needed to optimise. You can see that I trace the time taken here and this > is where I can say that, on the emulator, it takes 18 seconds. > Your draw method is fairly big. There are a lot of steps there, including a loop where you iterate through a bunch of points (the number of which you didn't specify, which might be your issue). You time nearly the entire method, but more than likely there is one or two lines in there that are eating up the bulk of that time. My suggestion to you was to profile your code so you can narrow down more precisely which part(s) of that block of code is where most of your time is being spent. If you can come back and say "this line in particular is killing me", or "l'm looping through 6,000 points each frame", then it will be easier to get help with optimizing. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
