geoxml "nozoom" option displaces infoWindowAnchor

[GoogleCodeExporter]

>What steps will reproduce the problem?
1. create a map from a kml file with option "nozoom" = true. 
2. in the kml file, add descriptions to the PlaceMarkers

>What is the expected output? What do you see instead?

the infoWindow is anchored near the bottom of the icon. By default, it should 
be located at the 
top of the icon. Specifying your own icon doesn't seem to help.

>What version of the product are you using? On what operating system?

7 May 2009. safari / ff2 macosx 10.4

>Please provide any additional information below.

temporary testlinks 
http://live.labforculture.org/2009/05/blogmap/test/test08-nozoom.html
http://live.labforculture.org/2009/05/blogmap/test/test08-zoom.html

Original issue reported on code.google.com by pike-common@kw.nl on 15 May 2009 at 5:26

[GoogleCodeExporter]

The default for icons are anchored the same as google maps icons are 
anchored... 
Specifying your own icon should help.. though there isnt yet support for doing 
so 
inside the kml.

Original comment by lanceala...@gmail.com on 15 May 2009 at 11:17

[GoogleCodeExporter]

Think I misunderstood...that behavior is wierd, because nozoom shouldnt have 
any 
impact without your examples I would have said they are unrelated.

Original comment by lanceala...@gmail.com on 16 May 2009 at 1:45

[GoogleCodeExporter]

Thanks for your response.

To make the report less ambiguous, I've removed the custom icon on two markers 
in the
KML of the example links. The same effect happens with "your" icons.

Oh .. and I found where. You override marker.showInfoWindowHTML if this.map is 
set in
line 3705 and below. If I dont pass "nozoom", this.map is not set (there), 
otherwise
it is set - dont know why. So if I dont pass nozoom, the original 
showInfoWindowHTML
is used, otherwise yours is used.

Your override reads
this.map.openInfoWindowHtml( this.getPoint(), html, opts ); }
which doesnt take the infoWindowOffset into account ?

I'm not sure *why* all that code is there, so I'm just going to workaround it 
in my
version :-)

*-pike

Original comment by pike-common@kw.nl on 19 May 2009 at 3:44