This is triggered by invokeAndBlock nesting which can lead to bad situations like this. I suggest adding a small delay to make sure that panning finished before you check bounds and start fetching. If the user is still dragging his finger you'd end up filling the device network queue completely.
You can use a timer to do the request and if you get a new drag event just cancel and resubmit the timer. We're also replacing some of the Map API's with asynchronous ones that are based on callbacks. These handle the communication with the native layer better. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/02fb8669-0234-4abf-bf2d-422ebf693a83%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
