On Feb 7, 1:55 am, Ben Appleton <[email protected]> wrote: > That's right - forwarding the event is fine, but it can be slow to provide > listeners with an event Object including a Point and LatLng. We considered > reusing Objects between calls, but that prevents the listener from storing > the Point/LatLng.
I do not suppose you might be willing to pass two separate Lat & Lng variables (by value) rather than one LatLng object (by name). It might be inconsistent but it would be quick - no garbage collection required - users could build their own LatLng objects if required. Perhaps you could have separate "slowmousemove" / "fastmousemove" event listeners. One for API purists. One for speed freaks. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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/google-maps-js-api-v3?hl=en.
