Dragging nodes in Linear view makes them disappear
Bug #245663 reported by
Lynoure Braakman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
semantik (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: semantik
Steps to reproduce:
1. Start with a mindmap with both child and sibling nodes
2. Drag a node to a new location in Linear view
Expected: Node to appear in the new location in the Linear view, resulting in a new order between siblings
What happened: The dragged node or subtree disappeared totally from the Linear view
Changed in semantik (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
I also came across this failure. Could easily happen by accident once the tree gets big enough. It also opens the gates to another failure After clicking on the dissappeared node in the map view again, where it is still present and correctly set as a child node, (after it lost focus by clicking on the other node) semantik 0.7.2 will crash with a segmentation fault!
I ran it on Kubuntu 10.04 LTS (dist upgraded a few days ago over a rather fresh 9.10 Kubuntu)
$ semantik -v
Qt: 4.6.2
KDE Development Platform: 4.4.2 (KDE 4.4.2)
Semantik: 0.7.2
$ lsb_release -ds
Ubuntu 10.04 LTS
$ uname -s -r -v -m -o
Linux 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 i686 GNU/Linux
Steps to reproduce:
1. start a mindmap
2. add two nodes A and B
3. select link-tool
3. press mouse on node A in map view and drag mouse to node B, release mouse button
expectation: B should now be child of A in the map view and the linear view
observation: as expected!
4. in linear view drag B onto A.
expectation: B should still be child of A in both views
observation: B dissapears in linear view, but is still visible in map view
5.a) if B is highlighted (thicker border) click at A
5.b) click on B again
SIGSEGV -> Segmentation Fault
I also tried this with the source-tarball of version 0.7.3 from http:// code.google. com/p/semantik/ downloads/ list
That version seems to resolve the bug!