Hi developers -

It is a known issue that both events fire on a double click:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=394

I've been unable to replicate the double_click event not firing at all
with 1.8b however. Please upload full MXML that replicates the issue
if you're still experiencing it.

Paul - You may want to try 1.8c. There was a zoom issue that we fixed
in that release that sounds like what you're describing.

- pamela


On Wed, Jan 7, 2009 at 3:16 PM, Paul Hastings <[email protected]> wrote:
>
> ragae wrote:
>> map.addEventListener(MapMouseEvent.DOUBLE_CLICK, onMapDoubleClick);
>> map.addEventListener(MapMouseEvent.CLICK, onMapClick);
>>
>> The onMapDoubleClick is being ignored and all events are directed to
>> the onMapClick.
>> I'm using the latest API 1_8b.
>
> yeah the map mouse events seem to be a bit flaky. yesterday i was seeing the
> exact same behavior, today i'm getting *both* events firing on a double click:
>
> http://www.sustainablegis.com/projects/tz/tzmap/
>
> and in ff3.05 getting some extra weird behavior, zooming in on some areas via
> double clicks is on occasion tossing the map ext way out to the NW (ie zooming
> in on warsaw the map ext will sometimes get tossed out to iceland or nearby
> north atlantic). chrome's not showing that behavior (though it does also seem 
> to
> be seeing both mouse events on a double click). haven't tested in IE yet.
>
> i'm not sure if this is a google maps thing as much s a flex/flash thing,
> slapping flex frontends on arcIMS servers i recall having to use the keyboard
> plus mouse click for some interactions.
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API For Flash" 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-api-for-flash?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to