Wasn't it eKiTeL who wrote: >If a GControl contains multiple elements shouldn't all those elements >be treated as part of one GControl in that the info window will not >position itself below them? > >I thought about implementing this but I don't see how how having >GControls nested within a GControl would make things any different than >just having the one containing GControl.
The example in the Google documentation has multiple elements. As it happens, it doesn't have any info windows, but if you add an infowindow to the Google example, the infowindow avoids opening under the GControl. http://code.google.com/apis/maps/documentation/examples/control-custom.ht ml Perhaps you're doing something else not quite right somewhere else. If you're lucky, that something else might be what's causing your page to not begin to think about working in MSIE8 and Google Chrome, and for your infowindows to correctly avoid your controls in Opera, and for Safari to crash and burn. Perhaps if you fix whatever's causing the different behaviours in different browsers you might get the Opera behaviour in them all. -- Mike Williams http://econym.org.uk/gmap -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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?hl=en.
