| Issue 330: | Removing child node while bEnableUpdate is false causes error | |
| 3 people starred this issue and may be notified of changes. | Back to list |
What steps will reproduce the problem? Actually have very complicated use case but suspect following: 1. Call enableUpdate(false) on tree 2. Add a node with children 3. Remove one of the children nodes 4. Call enableUpdate(true) on tree What is the expected output? What do you see instead? Expect child node with children (other then removed one) to be shown in tree. Get error instead. What version of the dynatree and jQuery are you using? dynatree 1.2.1 - jQuery 1.7.2 On what operating system and browser? Windows 7 - FireFox nightly Please provide any additional information below. See issue 326 which while slightly different exposes same problem. Render is being called from various places in the code without always checking if tree.bEnableUpdate is true. For now I have modified my copy to do this check in the render function itself rather then track down all callers of render and doing it at each one.
Oct 6, 2012
(No comment was entered for this change.)
Labels:
-Milestone-Release1.2.2 Milestone-Release1.2.x
May 1, 2014
As of 2014 Dynatree is feature frozen. Please have a look at Fancytree (sequel of DynaTree 1.x): chances are good that the problem was resolved / the requested featuer is already implemented. Please open a new issue there otherwise: https://github.com/mar10/fancytree
Status:
WontFix
May 3, 2014
(No comment was entered for this change.)
Labels:
-Milestone-Release1.2.x Milestone-Release2.0
|
Labels: Milestone-Release1.2.2