Hi TreKing > Are you reading from a local DB or pulling from the network?
It's a local db. > AFAIK, there is no good way of knowing when the user has panned or zoomed >(there are no related events) Well, this guys at Google should make this events available, I think they are very useful :) > No ay problem amigo. Si no sabes como decir algo en ingles, yo hablo espanol > <):-) (<- Sobrero Smiley) Muchas gracias. De todas maneras trataré de usar el ingles, y asi practico ;) On 28 oct, 02:07, TreKing <[email protected]> wrote: > On Wed, Oct 27, 2010 at 6:40 PM, Pikoh <[email protected]> wrote: > > - The delay happens when loading from the d to the overlay i.e. the while > > loop I wrote you up. And i've tried to load them from an array instead of a > > db but makes no difference. > > Loading and then drawing 400 items to show on a map is going to be > relatively slow, no matter where you're pulling the data from. You have to > reduce your data set to that which is actually necessary and no more. > > Are you reading from a local DB or pulling from the network? > > > You are right, I'm very new to android programming and I confused overlay > > item with overlay. > > It does takes some getting used to :-) > > Now i'm trying to do what TreKing suggested me, that is just showing the > > > overlays in the view area, but i found a problem finding when this view area > > changes because of panning or zoom. I'm googling it but no luck, hope > > TreKing teach me how to do it ;) > > Well, it depends on what you want to do. What I do is allow the user to find > stops in the viewable area with a minimum zoom allowed. It's a one-time > operation to find all stops that are available and with the area and zoom > restrictions it limits the data set to somewhere in the range of [0, 50]. If > the user pans or zooms, nothing else happens until they manually trigger > another search, which also clears out the old stops to prevent having an > excessive number of items around. > > If you want to dynamically update the map as the user pans and zooms, that's > more complicated obviously, though not impossible. > First things to look at are the various touch events in the map view and > overlay classes and the zoom controller. > > AFAIK, there is no good way of knowing when the user has panned or zoomed > (there are no related events). What I've seen people mention is that they > track the current values themselves then check each draw() call to see if > they've changed and respond accordingly. > > > BTW, i'm spanish and sometimes making myself understood is a bit hard :) > > No ay problem amigo. Si no sabes como decir algo en ingles, yo hablo espanol > <):-) (<- Sobrero Smiley) > > Buena suerte. > > ------------------------------------------------------------------------------------------------- > 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
