Rank: Newbie
Groups: Member
Joined: 10/10/2011
Posts: 1
|
I am working with the Treeview Demo Programming\Hierarchical DB Update and see some unexpected behavior:
- If I drag Local Disk (C:) to be after Local Disk (E:) I would expect it to appear at the level of the other nodes. Instead it goes under Local Disk (E:). Sometimes (I can't reproduce it) it disappears under E: and the only indication as to what happened is that a minus sign appears beside E:. If you click on the minus sign and then click on the resulting plus sign you see C:. I have seeen this behavior 2 or 3 times but cannot reliably reproduce the disappearing act.
- It seems to be impossible to drag an item and drop it after the last of its siblings. It ends up on the next higher level. For instance if you expand C: and grab My Documents and drag it to after Temp I would expect it to end up on the level of Temp. Instead it ends up on the next higher level, at the level of Local Disk C:.
Is this behavior designed? How can a user get an item into the last place among siblings?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
Both behaviors are by design. When you drag a node, it can be dropped:
1. As a child node of the current highlighted node;
2. If AllowDragReordering is set to true, it can be dropped in between two sibling nodes. You cannot drop it after the last sibling nodes;
Hope this helps. Please feel free to let us know if you have any more questions.
Thanks!
|