ranathunga / kml-samples

Automatically exported from code.google.com/p/kml-samples
0 stars 0 forks source link

Version 5 broken mouse over effects #233

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Which products are affected?

GE5 ignores the highlight style map whenever 
1) There is no text in the description tag. 
2) There are only spaces in the description tag. 
3) If CDATA is used, if there is only   in the description tag 
4) If <displayMode> is "hide" in the balloon style 

What steps will reproduce the problem?
1) Open Google Earth version 5. 
2) Use the toolbar to add a placemark. 
3) Do not enter any text into the "description". 
4) Test the placemark.  There are no mouse over effects. 
5) Now, edit the properties of the placemark.  Enter some text into the 
"description". 
6) Test the placemark.  The mouse over effects are working.

What is the expected output or behavior? What do you see instead?

Mouse over effects should not depend upon the presence or absence of a 
placemark description.

What application versions (if any) are you using?

Google Earth 5.0.11337.1968 (beta)
Build Date   Jan 29, 2009
Build Time   2:38:36 am
Renderer     OpenGL
Operating System  Microsoft Windows Vista (Service Pack 1)
Video Driver  NVIDIA Corporation (00006.00000.06001.18000)
Max Texture Size  4096x4096
Server  kh.google.com

Which operating systems and browsers are affected?

Please provide any additional information (code snippets/links) below.

Sample kml, created using the steps above.  There is a period in the 
description tag, so the mouse over effects are working.  If the period 
is removed, or if a <displayMode> hide is added to the balloonstyle, 
then the highlight style map is ignored. 

<?xml version="1.0" encoding="UTF-8"?> 
<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http:// 
www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" 
xmlns:atom="http://www.w3.org/2005/Atom"> 
    <Document> 
        <name>KmlFile</name> 
        <Style id="sn_ylw-pushpin"> 
            <IconStyle> 
                <scale>1.1</scale> 
                <Icon> 
                    <href>http://maps.google.com/mapfiles/kml/pushpin/ 
ylw-pushpin.png</href> 
                </Icon> 
                <hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/ 

            </IconStyle> 
        </Style> 
        <Style id="sh_ylw-pushpin"> 
            <IconStyle> 
                <scale>1.3</scale> 
                <Icon> 
                    <href>http://maps.google.com/mapfiles/kml/pushpin/ 
ylw-pushpin.png</href> 
                </Icon> 
                <hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/ 

            </IconStyle> 
        </Style> 
        <StyleMap id="msn_ylw-pushpin"> 
            <Pair> 
                <key>normal</key> 
                <styleUrl>#sn_ylw-pushpin</styleUrl> 
            </Pair> 
            <Pair> 
                <key>highlight</key> 
                <styleUrl>#sh_ylw-pushpin</styleUrl> 
            </Pair> 
        </StyleMap> 
        <Placemark> 
            <name>test mouse over</name> 
            <description>.</description> 
            <LookAt> 
                <longitude>72.95668542891266</longitude> 
                <latitude>19.17166745815817</latitude> 
                <altitude>0</altitude> 
                <range>4070.883142012721</range> 
                <tilt>0</tilt> 
                <heading>-0.006138090619769606</heading> 
                <altitudeMode>relativeToGround</altitudeMode> 
            </LookAt> 
            <styleUrl>#msn_ylw-pushpin</styleUrl> 
            <Point> 
                <coordinates>72.95668542891266,19.17166745815817,0</ 
coordinates> 
            </Point> 
        </Placemark> 
    </Document> 
</kml> 

Original issue reported on code.google.com by bill.cl...@earthpoint.us on 3 Feb 2009 at 10:22

GoogleCodeExporter commented 9 years ago

Original comment by api.roman.public@gmail.com on 3 Feb 2009 at 11:06

GoogleCodeExporter commented 9 years ago
Work around!

Add an ExtendedData tag to the placemark.  It just works.  Mouse-over effects 
are 
restored!
.
.
.
<Placemark> 
            <name>test mouse over</name> 
            <description>.</description> 
            <LookAt> 
                <longitude>72.95668542891266</longitude> 
                <latitude>19.17166745815817</latitude> 
                <altitude>0</altitude> 
                <range>4070.883142012721</range> 
                <tilt>0</tilt> 
                <heading>-0.006138090619769606</heading> 
                <altitudeMode>relativeToGround</altitudeMode> 
            </LookAt> 
            <styleUrl>#msn_ylw-pushpin</styleUrl> 
            <ExtendedData></ExtendedData>
            <Point> 
                <coordinates>72.95668542891266,19.17166745815817,0</ 
coordinates> 
            </Point> 
        </Placemark> 
.
.
.

Original comment by bill.cl...@earthpoint.us on 9 Apr 2009 at 5:19

GoogleCodeExporter commented 9 years ago
This has been fixed in Version 5.0.11733.9347 downloadable from Google Earth 
download
page. GE doesn't seem to automatically update - is this intentional while still 
a
beta or is it another issue

Original comment by Bushy2...@gmail.com on 9 May 2009 at 2:40

GoogleCodeExporter commented 9 years ago
Its not completely fixed. If the point does not have a discription (or 
ExtendedData
work around) then it is not clickable to bring up the balloon. Also it doesn't 
have
the same "bounce" animation on mouse over.

Original comment by dalemar...@gmail.com on 9 May 2009 at 3:45

GoogleCodeExporter commented 9 years ago
Yes I can confirm dalemartyn's observation re animation and that the balloon 
will not come if there is no 
description or extended data add in. I also queried this separately a few days 
ago under my name.

The problem may be more extensive with difficulties with hotSpots not having 
any effects.

I will post this separately though.

BobJ

Original comment by b_jor...@xtra.co.nz on 10 May 2009 at 1:35

GoogleCodeExporter commented 9 years ago
Ignore the hotSpot comment - operator malfunction - hotSpots must be outside 
the <icon> pair  :-(

Original comment by b_jor...@xtra.co.nz on 10 May 2009 at 2:50

GoogleCodeExporter commented 9 years ago

Original comment by api.roman.public@gmail.com on 11 May 2009 at 9:04