Changing the z-index on mouseover

[GoogleCodeExporter]

This is a feature request.

Let's look at the example at http://gmaps-utility-
library.googlecode.com/svn/trunk/labeledmarker/1.1/examples/markerhider.htm
l

Here, you can see that several markers are put over each other so that you 
can't see their labels.

My idea was (well, it worked for some degrees but not perfect) that the z-
index should be increased if I move over a label with the mouse.

So you have do do this: Assign a mouse over handler to all labels (if you 
wish to) and set the z-index of the image and label text to a high value 
when inside it. When leaving the marker just set it down to the original 
value.

With this it should be easy to read all the markers in your example (and 
in my application, of course ;).

What do you think?

JOERN

Original issue reported on code.google.com by joern.h...@gmail.com on 9 Oct 2007 at 9:04

[GoogleCodeExporter]

Here's a patch for the newest SVN version.
It was built using the fact, that the marker image is the previous sibling, so 
perhaps there's a better way of getting this (through the superclass).

Original comment by joern.h...@gmail.com on 12 Oct 2007 at 8:30

Attachments:

• zindex.patch

[GoogleCodeExporter]

Original comment by lem...@gmail.com on 23 May 2008 at 4:12

• Added labels: Class-LabeledMarker

[GoogleCodeExporter]

Original comment by lem...@gmail.com on 23 May 2008 at 6:41

• Changed state: Accepted
• Added labels: Type-Patch
• Removed labels: Type-Defect

[GoogleCodeExporter]

I'm wondering why there's no interest in this issue.
To see it in action you can look at http://www.kreisalarm.de/drkmap/ (zoom in 
to the 
even more examples of the need for it).

Original comment by joern.h...@gmail.com on 11 Jun 2008 at 9:28

[GoogleCodeExporter]

Cool-- I'll admit I hadn't taken a look at your example. I'm concerned about 
the use
of previousSibling-- this is an implementation detail and could change. Could 
you
look into using zIndexProcess instead? (It's in the API reference).

Original comment by pamela.fox on 11 Jun 2008 at 9:35

[GoogleCodeExporter]

The zIndexProcess is used to set the zIndex at creation time.
The idea of changing the zIndex on mouseover can't be solved by using the map 
API I
think. For that I can't see a better way of "hacking". It's up to the official 
Google
Maps developers to implement a better way. Perhaps this issue has to be raised 
in the
official Google Map API groups?

Original comment by joern.h...@gmail.com on 11 Jun 2008 at 9:48

[GoogleCodeExporter]

Disclosure: I work for Google.

The zIndexProcess function is currently called at creation time and 
additionally when
the info window is opened/closed over a marker. We can modify the API to make 
it so
that function could be evaluated at other times as well. 

But yes, that'd be a file to issue at gmaps-api-issues.google.com

Original comment by pamela.fox on 11 Jun 2008 at 9:54

[GoogleCodeExporter]

"Disclosure: I work for Google." - I know. That's the reason I tried to re-open 
this
issue. I can talk directly to Google ;)

Can you file this issue at gmaps-api-issues or should I?

Original comment by joern.h...@gmail.com on 11 Jun 2008 at 10:00

[GoogleCodeExporter]

Please file it. It makes it look like developers care about issues, and not 
just me. :)

Original comment by pamela.fox on 11 Jun 2008 at 10:09

[GoogleCodeExporter]

I haven't committed the patch it because of the previousSibling issue, as well, 
and there are only so many hours 
of my free time. :)  This is definitely something I think we should do.  See 
also Issue 29 re: http://esa.ilmari.googlepages.com/ZMarker2.htm

Original comment by lem...@gmail.com on 11 Jun 2008 at 6:44