Closed GoogleCodeExporter closed 9 years ago
Thanks for the additional details on this new issue. You can keep track of the
status of this at issue #492
Original comment by jli...@google.com
on 4 Jan 2011 at 9:14
Hi, I'm a developer for Google Earth.
Yes this is a known bug and we are working on fixing it.
We also have a workaround/fix that will be forward compatible for you! The
trick here is that you will need to create your IconStyle using <kml> text.
As gpsanimator correctly notes, there is an undocumented tag that is being
assigned to the <IconStyle> which will be released in a future client which is
<gx:headingMode>. <gx:headingMode>screenUp</gx:headingMode> is assigned by
default iff the <heading> value is initially 0. If the value is something other
than 0, <gx:headingMode>northUp</gx:headingMode> is being assigned.
Read that again.
Okay still with me? The reason why we do it this way is to emulate the way that
earth used to use IconHeading before we had explicit heading modes.
Unfortunately it also means that as soon as the headingMode is assigned it's
(semi)permanent as far as the js developer is concerned.
Workaround:
Create your <IconStyle> with <gx:headingMode>northUp</gx:headingMode> as kml
text and parse it with the appropriate javascript apis (ge.parseKml() I assume).
Original comment by zach.vor...@gmail.com
on 6 Jan 2011 at 4:18
Zach
Thank you for your help. This fixed the problem for me but created a new one.
I have not played around much, but it seems that I can not use this method
"inline" in the placemark while inheriting attributes from a global style.
Example, I can not make a style, referenced with <styleUrl> then modify just
the heading inline in the placemark.
Do you know of an easy way around this without having to modify all my styles
in-line when rotation is desired? I would love to set color/icon/hotspot
globally and just mod heading in the placemark <Style> tag.
Brings me to another question. How far back does this tag work? I'm using GE
EC 5.1.3533.1731 and it works.
Is there any way we can expedite the "documented" nature of this feature so we
can all use it? Example, from what I read in your comment, it sounded like to
make "90" point "East" that I wanted to use northUp, but I'm using screenUp and
90 points East.
Original comment by mccon...@gmail.com
on 27 Jan 2011 at 8:43
Original issue reported on code.google.com by
gpsanima...@gmail.com
on 27 Dec 2008 at 7:24Attachments: