My favorites | Sign in
Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 233: network links: placemarks reappearing after its parent kml has being removed
7 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Type-Defect
Priority-Medium
Internal-1795786
Component-Plugin


Sign in to add a comment
 
Reported by christian.leyen, Apr 22, 2009
What steps will reproduce the problem?
1.load kml into a network link and click on any placemarks belonging to
this kml
2.remove the kml (removeChild)
3.load another kml into the nertwork link
4.after some time (ie, after clicking on placemarks on the second kml)
placemarks that have being clicked in the first kml will reappear

What is the expected output or behavior? What do you see instead?
removed placemarks should be gone forever... :-)


Which plugin version are you using?
5.0.11655.6079 (I didn't notice this in earlier versions)


Which browsers and operating systems are affected?
tested in FF3 and Chrome


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

Try this: http://www.parlamentodasaguasrs.com.br/kmlTest.php
Click on placemarks and change kml (using "kml1" and "kml2" buttons).
Placemarks of removed kml will reappear.

Comment 1 by api.roman.public, Apr 22, 2009
(No comment was entered for this change.)
Status: Accepted
Labels: Internal-1795786
Comment 2 by graham.waddingham@bt.com, May 01, 2009
Similar issue here - this time with network links that update on map change. Click 
on one of its polygons, then move the map. The network link then updates, to create 
a new set of polygons, but the one clicked on the original set remains.
Comment 3 by api.roman.public, May 01, 2009
A workaround is to setVisibility(false) before removal.
Comment 4 by apoder...@uoc.edu, May 03, 2009
I'm experiencing this problem with a networkLink and "VIEW_REFRESH_ON_STOP". Every
time you click on a Placemark (and open its balloon) it is duplicated over and over
again. It's not possible to remove these duplications removing all the childNodes or
even setting visibility to false. Also these duplications not give response to any
event listener.

I'm working on Windows (GE Plugin 5.0.11655.6079, Firefox 3.0.10 and IE 7.0.5730.11).

Comment 5 by api.roman.public, May 04, 2009
Hi apoderoso,

That may be  Issue 59  coming back again. Can you check that issue and comment there?
If it's happening again I'll reopen it.

Thanks,
Roman
Comment 6 by api.roman.public, May 21, 2009
(No comment was entered for this change.)
Labels: Component-Plugin
Comment 7 by api.roman.public, Aug 08, 2009
(No comment was entered for this change.)
Status: Confirmed
Comment 8 by api.roman.public, Aug 08, 2009
Bulk edit.
Comment 9 by api.roman.public, Aug 08, 2009
I believe this is fixed in 5.0.11738.1858; if this is still coming up, please ping
the issue.
Status: Fixed
Comment 10 by geoneubie, Aug 11, 2009
I am having issues removing network links after clicking on a feature and viewing its
placemark.

Go to:
http://ngdc.noaa.gov/metadata/published/19115/NOSA/kmlList.html

Click on Baseline Surface Radiation Network (BSRN) and then click on a feature.
Now click on Global-USGODAE-BUOYS (GODAE), and
then Clear Extents.  

After a delay one of the BSRN features redisplays after the clear and new Clear
Extents attempts do not work.




Comment 11 by api.roman.public, Aug 11, 2009
Thanks for the repro steps, confirmed still a bug.
Status: Confirmed
Comment 12 by api.roman.public, Aug 12, 2009
(No comment was entered for this change.)
Status: FixedNotReleased
Comment 13 by luizrodrigotozzi, Aug 19, 2009
Any ideas when it will be released?
Thanks!
Comment 14 by api.roman.public, Aug 19, 2009
We generally don't announce release dates, sorry Luiz :-(
Comment 15 by luizrodrigotozzi, Aug 19, 2009
No problem... My question is not about an specific date, but if it will be in the
next one :)
Thanks again!
Comment 16 by api.roman.public, Aug 19, 2009
Ah, yes-- should be fixed in the next release.
Comment 17 by api.roman.public, 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
Sign in to add a comment