Bug 139904 - Asynchronous Message arrows arbitrary relationships
Summary: Asynchronous Message arrows arbitrary relationships
Status: RESOLVED DUPLICATE of bug 330609
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2007-01-11 14:45 UTC by Adrian.L.Parker
Modified: 2015-03-08 09:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.14.3 (KDE 4.14.3)

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian.L.Parker 2007-01-11 14:45:49 UTC 
Version:           1.5.51 (using KDE KDE 3.5.3)
Installed from:    Compiled From Sources
Compiler:          gcc version 4.1.1 20060525 
OS:                Linux

When creating a sequence diagram, if you place multiple Asynchronous message arrows, moving one arrow often causes other Asynchronous arrows to move (when you have selected only one).

When moving one arrow, the other arrow that it moves is not necessarily the next closest arrow.
Comment 1 Achim Spangler 2007-01-11 15:20:24 UTC 
Hi,
this problem is caused by the selection handling algorithm.
Try the following workaround, until somebody gets time to fix this:
Click with your mouse at _background_ between switching from one selected item to the other.

Problem reason:
The state engine for selection handling handles your click on the next item as a selection-extension (as if you would hold CTRL during your next click).

Hope this workaround helps,
Achim
Comment 2 Adrian.L.Parker 2007-01-11 16:35:32 UTC 
This is for version 1.5.51.

Sorry I missed entering that.
Comment 3 FiNeX 2009-08-09 16:28:32 UTC 
The bug is still reproducible on trunk
Comment 4 Natanael Arndt 2013-05-17 10:05:45 UTC 
This is still reproducible with Version 2.8.4 Using KDE Development Platform 4.8.4
Comment 5 Ralf Habacker 2015-03-08 09:33:37 UTC 

*** This bug has been marked as a duplicate of bug 330609 ***