Closed CompSciFutures closed 9 years ago
Thanks for reporting. We are aware of this issue and I'm working on a solution as we speak.
The issue is that the WITH
command is currently not being sent in a lot of commands. This is a separate issue. The referenced PR only ensures that the state of the Mesh itself is updated correctly.
Fab, yell out when you have something to test.
@aprender I made a quick fix. 6fff5ce should work for now. I'm working on a bigger refactor though.
Hi Alex,
Thanks for doing it so quick - I tested that fix and its a little too successful at deleting things! It very neatly resolves the problem described in the initial example as well as deleting everything from the scene.
So allow me to provide a revised piece of code ;)
--- CUT ---
(Previous code block that was here has been moved to #443 as its a separate bug)
@alexanderGugel tested against last night's develop branch (a5d7fd552505c0f2d40c4a86aa0a61950736ff16) problem still exists.
Description
Calling dismount() on a Node() that is a parent of a Mesh() does not remove the mesh from a scene. Instead, the Mesh remains in the scene and any components along that same chain are no longer updated, thus any animated transformations applied to the mesh seem to "freeze".
I have encountered some other more obscure examples of generalised weirdness when dismount()ing meshes, but hopefully they are all part of this same bug. Will test a few things again once a fix comes through.
Steps to Reproduce
Isolation
Problem exists in:
Code Example
In this complete example, a wire-frame cube should spin for 3 seconds then disappear. Instead it freezes in place after 3 seconds.
See
oCubeNode.dismount();
below: