| Issue 131: | Icon heading displayed incorrectly. | |
| 8 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
What steps will reproduce the problem? 1. run the first attached html file, posTgtPt01.htm in a browser and observe the orientation of the arrow - straight up. 2. Close the session and open the second file, posTgtPt02.htm in the browser. This is identical to the first but with the heading of the icon and the LookAt increased by 45 degrees. The Icon is no longer straight up, but at an angle to the left. What is the expected output or behavior? Expect to see the Icon still straight up as we have changed the heading of both the Icon and the lookAt by the same amount. What do you see instead? The Icon is now angled at around 45 degrees to the left. I have tested further values - from 0 to 45 the variation increases to the left, from 45 to 90 it decreases to 0, from 90 to 135, it increases to the right and from 135 to 180, it decreases back to zero. From 180 to 360 the pattern is repeated. This bug was introduced in the version that first exhibited the Icon Name incorrect orientation that we reported in bug report 113. At the time we thought we had a bug in our code, but the above test demonstrates otherwise. Which plugin version are you using? Current - 4.3.11528.8566 Which browsers and operating systems are affected? FireFox 3.0.5, IE 6.0.2900 Please provide any additional information (code snippets/links) below. In previous versions and the current Google Earth, the icon is displayed as a flat object in a plane that remains perpendicular to the LookAt irrespective of the lookAt's orientation. In this version of geplugin the plane of the icon appears to vary depending on the lookAt's orientation. |
||||||||||||||
,
Jan 05, 2009
(No comment was entered for this change.)
Status: Accepted
Labels: Internal-1565373 |
|||||||||||||||
,
Feb 08, 2009
You may have fixed this in development, but if not, I have a thought on what mey be causing this. I had a similar problem - of directions not being true at different angles ... they were OK at the Cardinal points (N,S,E,W) and furthest off at NE,SW,SW and NW. That was caused by me incorrectly converting from distance (metres) North and East to lat/lon degrees, by MULTIPLYING the distance East (along the latitude) by cos(lat) INSTEAD OF DIVIDING by cos(lat) (D'OH). Just a thought. I'm REEEEALLY looking forward to a fix! Cheers, |
|||||||||||||||
,
Apr 01, 2009
Fixed as of 5.0.11655.6079. http://code.google.com/apis/earth/documentation/releasenotes.html#2009-03-31
Status: Fixed
|
|||||||||||||||
,
Apr 03, 2009
I don't think you have fixed this issue in Google Earth Plug-in, version 5.0.11655.6079. My program still displays the icons incorrectly. When I downloaded the two examples in my initial report (above) - they still display the documented mis-behaviour. Specifically, posTgtPt02.htm displays the arrow pointing off to the left. |
|||||||||||||||
,
Apr 06, 2009
Repro'd. Looks like we missed something. Apologies for the misinformation.
Status: Accepted
|
|||||||||||||||
,
May 21, 2009
(No comment was entered for this change.)
Labels: Component-Plugin
|
|||||||||||||||
,
May 21, 2009
(No comment was entered for this change.)
Labels: Component-Rendering
|
|||||||||||||||
,
May 21, 2009
(No comment was entered for this change.)
Labels: -Component-Plugin
|
|||||||||||||||
,
Aug 08, 2009
(No comment was entered for this change.)
Status: Confirmed
|
|||||||||||||||
,
Aug 08, 2009
Bulk edit. |
|||||||||||||||
,
Aug 08, 2009
(No comment was entered for this change.)
Status: FixedNotReleased
|
|||||||||||||||
,
Sep 09, 2009
Fixed as of 5.1.3506.3999 (API v1.003); see announcement here: http://groups.google.com/group/google-earth-api-notify/browse_thread/thread/6a32fdfcc60236e If this issue is still not fixed, please let us know.
Status: Fixed
|
|||||||||||||||
,
Sep 09, 2009
"Fixed as of 5.1.3506.3999 (API v1.003)" No, I'm afraid not... My problem demo at the top of this thread still misbehaves as before. I'm convinced this bug is all but unfixable, given the complex behaviour of Placemark icons (2D objects in a 3D world and auto scaling depending on camera range), so I have moved away from placemark icons to represent the target in my animations to using models - which are just fabulous! My real bugbear is the "near clipping plane" bug (not strictly Plugin I know) which I would LOVE you guys to crack. Keep up the good work - it's a fabulous product. |
|||||||||||||||
,
Sep 09, 2009
Urgh :-) This bug is haunting me. Will check into this again soon.
Status: New
|
|||||||||||||||
,
Sep 18, 2009
(No comment was entered for this change.)
Labels: -Internal-1565373 Internal-2131490
|
|||||||||||||||
,
Nov 08, 2009
My project is based on the placemark icon heading using the map heading as specified in the API reference. I think, before 5.1, the heading worked correctly, i.e. using the map heading, not the screen heading. Please fix it soon! |
|||||||||||||||
,
Nov 24, 2009
Can the latest problem reporters verify this with 5.1.3533.1731?
Status: Fixed
|
|||||||||||||||
,
Nov 24, 2009
Well done you guys ... my reported error is resolved in 5.1.3533.1731. Thanks for the dedication. Unfortunately it doesn't help me as I long ago abandoned using placemark icons to represent my target locations and am having lots of success with using models. Now, please, oh! please, can you fix the "near clipping plane" issue #120 which was reported before this one (Dec 12 08) and has been confirmed as a bug. |
|||||||||||||||
,
Nov 25, 2009
Because after 5.1 icon heading behaves different, I think there should be two options for icon heading: 1. Do not rearrange the heading of placemark after view has been changed. It means placemark anchored and can not turn. 2. Always follow the screen top edge. |
|||||||||||||||
,
Nov 30, 2009
>>Can the latest problem reporters verify this with 5.1.3533.1731? No. I have updated to 5.1.3533.1731 and there is no change. The bug is described in detail in my post: http://groups.google.com/group/google-earth-browser-plugin/msg/c0b4f37125c2df77?hl=en In comment 19, serhatalyurt suggests two options: Option 1 is how the GE application works, confirmed by the KML reference, and how the API used to work. Option 2 is how it works in 5.1.3533.1731 Two options would be OK but if only one option is possible, option 1 should be the one ,being in line with the GE application and the KML reference. |
|||||||||||||||
,
Dec 08, 2009
I see, despite two recent posting 19 and 20, the issue's status is still "fixed", ,when clearly it is not. |
|||||||||||||||
,
Dec 09, 2009
Still an issue with 5.1.3533.1731. Used to work with version 4. Now icon rotates with the screen, where it is supposed to have the geographic heading. |
|||||||||||||||
,
Dec 22 (2 days ago)
I am using Google Earth Pro v5.1.3509.4636 (beta) and it's not working. barryhunter (KML Guru) at the developer forum pointed me to this post. I am attaching 2 images. Image1.png is the correct orientation of the arrows with N arrow pointing at 0 degree. Image2.png is the in-correct orientation of the arrows with N arrow pointing at 90 degree (based on diagram on this page: http://code.google.com/apis/kml/documentation/kmlreference.html#headingdiagram) |
|||||||||||||||
,
Dec 22 (46 hours ago)
I'm satisfied that the problem as stated has been solved. I'm not sure what problem is being reported by Cyclope above as we can't see the issue in GE - a png image doesn't do it full justice. My interpretation of the icon behaviour is that its orientation follows the orientation of the Navigation Control, but it remains in the plane of the camera (or screen) and follows some undocumented rules about sizing - but which roughly keeps it visible at all ranges. I would also point out that his reference is related to the orientation of the lookAt, not the Icon, which is a bit confusing. |
|||||||||||||||
,
Today (11 hours ago)
If you "view" or "download" Cyclope's two pngs, , the issue is clear, the wind direction icons do not follow the orientation of the Navigation Control but it remains in the orientation of the screen. Here is another example of the problem: |
|||||||||||||||
,
Today (11 hours ago)
Oops! |
|||||||||||||||
|
|
|||||||||||||||