You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removal of point entities from the viewer is broken after calling viewer.flyTo() or viewer.zoomTo(): Sandcastle Example
(Edit: It's not the flyTo method, see my comment below)
After removing the entities from the viewer they get "stacked" in the center of the screen and stay there if flyTo/zoomTo was called before the removal. As far as I have tested it doesn't matter what the target of the flyTo/zoomTo method is and how many points are added to the scene. Other entity types seems to be not affected.
I might have a look at it but from a first glance at the correspoding code I think someone else might be faster with fixing this ;)
The text was updated successfully, but these errors were encountered:
I just found out that my first impression was wrong. It is not the flyTo/zoomTo method that's causing the problem (will edit the title).
The example i gave above can also reproduce the error without using the flyTo method, but it's harder to achieve. You have to zoom in to where the point were and then zoom out again. Gif (without using viewer.flyTo()):
UniquePanda
changed the title
flyTo/zoomTo method breaks removal of point entities
Removal of point entities broken
Dec 4, 2018
Removal of point entities from the viewer is broken
after calling viewer.flyTo() or viewer.zoomTo():Sandcastle Example
(Edit: It's not the flyTo method, see my comment below)
After removing the entities from the viewer they get "stacked" in the center of the screen and stay there if flyTo/zoomTo was called before the removal.
As far as I have tested it doesn't matter what the target of the flyTo/zoomTo method is and how many points are added to the scene. Other entity types seems to be not affected.I might have a look at it but from a first glance at the correspoding code I think someone else might be faster with fixing this ;)
The text was updated successfully, but these errors were encountered: