Hi, So you are doing something similar to my draw method?
I have just tested without alpha and anti-alising and it is faster, but when there is big zoom level the mapactivity is closed (i think this is due to memory usage) How should i profile this case? Really as i said there is not any strange thing on the code... Simply a map with an overlay... Thanks! On 1 jul, 01:39, TreKing <treking...@gmail.com> wrote: > On Thu, Jun 30, 2011 at 5:47 PM, Felix Garcia Lainez < > > fgarcialai...@gmail.com> wrote: > > About the size with 300 or 400 GeoPoints i am already having problems... > > The method isOnePointVisible is an optimization i did in order to try to > > improve performance (seems to work fine). > > So I have a very similar overlay to draw routes, with no optimization, and I > just loaded 7 or 8 of them with no apparent slow down on my Nexus One. > > Here are some thoughts: > - What device are you running on? > - Are you debugging or is this in release mode? > - Do you need anti-aliasing? I think that might slow it down. > - Do you need alpha? That would definitely slow down drawing. Set that to > solid and see if if helps. > > If none of that helps you're going to have to profile your code to get a > clear picture of what's taking so long. > > --------------------------------------------------------------------------- > ---------------------- > 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
