Closed coreyo closed 13 years ago
The 'idle' event is not limited to panning and zooming, as triggered by the user interface. Any programmatic calls including the 'resize' event and fitBounds() function also trigger an idle call upon completion. The map must be made to hold extra state and be intelligent enough to know when to do nothing if an idle event is triggered with no significant state change.
As the Map View loads, various unexpected idle events are triggered causing the map to re-request the same result-set multiple times.