More filtering or information on mouse events

[GoogleCodeExporter]

Currently you get a click event for pretty much any mouse action that happens 
over the plugin, even if it wasn't a click event (eg: the mouse wheel was 
scrolled, the view was rotated by a drag and drop etc). It would be more useful 
if you only got a click event when a click actually occured. Also you get click 
events if the user clicks in a javascript alert box which happens to be over 
the plugin - it seems like you should not get click events for clicks on other 
windows even if they're over the map? Maybe there just needs to be more 
infromation in the mouse event object to allow devs to identify where the click 
came from.

Requested by: TinyGrasshopper

Supported by: , jan.wischnat

Original issue reported on code.google.com by api.roman.public@gmail.com on 12 Aug 2008 at 8:46

[GoogleCodeExporter]

Another place where more information in the mouse events would be useful is 
when the
user clicks on a placemark but there is more than one placemark under the mouse.
Currently you get a globe click event for the first click and then a placemark 
click
event when the user selects a placemark from the cloud of placemarks that gets 
expanded.

It is currently quite difficult to filter out the first globe click as you cant 
tell
that they really were trying to click on a placemark.

Original comment by cds...@gmail.com on 14 Aug 2008 at 1:24

[GoogleCodeExporter]

Original comment by api.roman.public@gmail.com on 5 Feb 2009 at 8:15

• Changed state: Accepted
• Added labels: Internal-1633894, Type-Defect
• Removed labels: Type-Enhancement

[GoogleCodeExporter]

Original comment by api.roman.public@gmail.com on 22 May 2009 at 1:48

• Added labels: Component-Plugin

[GoogleCodeExporter]

Original comment by api.roman.public@gmail.com on 9 Aug 2009 at 12:52

• Changed state: Confirmed

[GoogleCodeExporter]

Bulk edit.

Original comment by api.roman.public@gmail.com on 9 Aug 2009 at 1:02

[GoogleCodeExporter]

Issue 311 has been merged into this issue.

Original comment by api.roman.public@gmail.com on 2 Sep 2009 at 5:03

[GoogleCodeExporter]

Mouse events should also support units fractional_pixels and insert_pixels
When the entire layout is done in fractional units then the mouse x and y 
values are
not usable and need to be converted to fractional units.

However, for this we need to know the GEWindow width which is not available. A
workaround is to find out the map3d div offsetwidth but that width is only 
valid if
the browser is not zoomed in or out. Browser zoom scales pixels thus not 
breaking any
javascript code. however, pixels in ge remain true pixels and we just get more 
of them.

Original comment by vandint...@gmail.com on 27 May 2010 at 11:27

[GoogleCodeExporter]

Issue 220 has been merged into this issue.

Original comment by bcke...@google.com on 15 Feb 2011 at 2:27

[GoogleCodeExporter]

Original comment by api.roman.public@gmail.com on 28 Jul 2011 at 4:08