Wasn't it String who wrote: > >On Jan 24, 9:58 am, marcelo <[email protected]> wrote: > >> I wouldn't recommend doing that. >> Such a trick would show an icon that is away from its anchor, and the >> infoWindow anchor as well as the icons clickable area would still be >> defined as if it was a 32x32 image. >> It is much better to do as Larry suggested, using one of the other >> parsers, which expose the internal objects. > >Those compromises will exist, it's true, but that's the best that you >can do with the GGeoXml object - which the OP specified.
It might be possible to do slightly better, if you don't mind going quite deep into undocumented territory, by intercepting the "addoverlay" events when GGeoXml adds the markers to the map. http://econym.org.uk/gmap/interceptor.htm What you'd like to do is to grab the details from the "addoverlay" event, create your own GMarker with the same location and infowindow, and then destroy the original one. The first to parts of that are OK but getting rid of the original marker is a little trickier. You can't just removeOverlay() or hide() the original marker, because GGeoXml now contains some sort of crude overlay management, and may well add it back at a later point when the map moves. Similarly you can't really destroy the original GMarker object, because the GGeoXml overlay manager might get upset about that. One possibility would be to .setLatLng() the original marker to an impossible location, such as North of the North Pole. I've not tried it. -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
