Version 1.7.9 beta 3 (Windows 7)
What steps will reproduce the problem?
1. At start we have one node with one childnode
2. Next, we move last childnode near to root node by "shift+left" hotkey and
parent and child became siblings.
3. Then the tree cursor on first node:
A) we can type "left" hotkey and there is no move to the parent of first node
(as i expect).
B) we can type "right" hotkey and move to the next sibling (i expect no move)
This behavior of first node continues after other operations with tree.
I can normalize it by creating new childnode of this node and removing it.
But it's very big problem for macroses (Autoit), scripts and other automations.
I will be happy, when you repair this.
Original issue reported on code.google.com by smogen...@gmail.com on 26 Aug 2012 at 7:28
Original issue reported on code.google.com by
smogen...@gmail.comon 26 Aug 2012 at 7:28