Hello,
I'm trying to fill nodes on server on "On demand" mode. It works fine when my node has no children. But if it has children - they will be duplicated.
Scenario: TreeView has node "Root" and child "Node1". I click on "+" near "Root". Server gets event. The event adds nothing. TreeView expands with 1 child. This works fine until postback. After postback "Root" has 2 children "Node1"!
It looks like a bug or I'm doing somthing wrong.
I wrote small function to remove duplicates each time on load but maybe there is a better way for me to prevent duplicate appearing? I'll appreciate any idea on this.
Thanks,
Eugene
I'm trying to fill nodes on server on "On demand" mode. It works fine when my node has no children. But if it has children - they will be duplicated.
Scenario: TreeView has node "Root" and child "Node1". I click on "+" near "Root". Server gets event. The event adds nothing. TreeView expands with 1 child. This works fine until postback. After postback "Root" has 2 children "Node1"!
It looks like a bug or I'm doing somthing wrong.
I wrote small function to remove duplicates each time on load but maybe there is a better way for me to prevent duplicate appearing? I'll appreciate any idea on this.
Thanks,
Eugene
2 Answers, 1 is accepted
0
Anthony
Top achievements
Rank 1
Rank 1
answered on 20 Nov 2008, 08:01 PM
Our company is having a similar problem with the RadTreeView.
1. We drag a root node to a drop target, and that event loads child nodes for the root, but does NOT expand the node.
2. We then expand the root node, which displays the appropriate number of child nodes.
3. We then drag the same root node tot he same drop target, and that event DOES NOT load the child nodes (the count is checked prior to loading), but there is now a duplicate number of child nodes under the root.
1. We drag a root node to a drop target, and that event loads child nodes for the root, but does NOT expand the node.
2. We then expand the root node, which displays the appropriate number of child nodes.
3. We then drag the same root node tot he same drop target, and that event DOES NOT load the child nodes (the count is checked prior to loading), but there is now a duplicate number of child nodes under the root.
0
Accepted
Paul
Top achievements
Rank 1
Rank 1
answered on 02 Dec 2008, 08:17 PM
Anthony is a colleague of mine and I wanted to follow-up and say that updating to the latest telerik build (Version 2008.3.1105.20) fixed this issue for us.
Thanks.