search

jsoliveira / javaapiforkml

Automatically exported from code.google.com/p/javaapiforkml
0 stars 0 forks source link

Unable to Add <gx:balloonVisibility> for AnimatedUpdate in Tour #23

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.
2.
3.

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

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

Please provide any additional information below.

 am trying to find for a way to get set  output the <gx:balloonVisibility> tag and set it to 1 under Update/Create under AnimatedUpdate for Placemark in Touring

Is there any way to get this?

Original issue reported on code.google.com by friendsh...@gmail.com on 14 Aug 2010 at 4:14

GoogleCodeExporter commented 8 years ago 
I am having the same issue.  Looking at the javadocs for 
de.micromata.opengis.kml.v_2_2_0.gx, which I assume is a mapping to all of the 
objects specific to the Google namespace (which 
<gx:balloonVisibility>0</gx:balloonVisibility> is a part of) it is not there.  
There are a lot of other objects missing from the gx namespace as well:

gx:altitudeMode
gx:altitudeOffset
gx:angles
gx:balloonVisibility
gx:coord
gx:delayedStart
gx:drawOrder
gx:duration
gx:h
gx:interpolate
gx:MultiTrack
gx:outerColor
gx:outerWidth
gx:TimeSpan
gx:TimeStamp
gx:Track
gx:ViewerOptions
gx:option
gx:w
gx:x
gx:y

Am I misunderstanding something, or does this API not completely implement the 
full http://code.google.com/intl/de/apis/kml/schema/kml22gx.xsd schema?

Original comment by lax...@hotmail.com on 9 Dec 2010 at 11:54

GoogleCodeExporter commented 8 years ago 
nope it doesnt work... i tried everything the past 3 days... won't work

i have a workaround that is very dumb but seems to fix this behaviour ... just 
delete everything you just loaded in the javascript and load again... then the 
balloons appear,.... strange behaviour

Original comment by nikolaus...@gmail.com on 11 May 2011 at 1:37

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
... they didn't update the API to reflect the latest google xsd.

Original comment by steffen....@gmail.com on 5 Nov 2011 at 10:08

GoogleCodeExporter commented 8 years ago 
it's because of the xal namespace

Original comment by Wilfried...@gmail.com on 14 Dec 2011 at 5:19