Bug 158087 - Resize of synchronous message bottom in sequence diagram causes top Y position to move in unknown way
Summary: Resize of synchronous message bottom in sequence diagram causes top Y positio...
Status: RESOLVED DUPLICATE of bug 330609
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-20 09:12 UTC by Robert Lugg
Modified: 2015-03-08 09:52 UTC (History)
1 user (show)

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

Attachments
xmi file shown in the following two attachments (15.53 KB, application/octet-stream)
2008-02-20 09:16 UTC, Robert Lugg 		Details
message to resize is circled (20.30 KB, image/png)
2008-02-20 09:17 UTC, Robert Lugg 		Details
Dragging bottom down causes top of message to move. (21.88 KB, image/png)
2008-02-20 09:19 UTC, Robert Lugg 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Lugg 2008-02-20 09:12:46 UTC 
Version:           2.0.0 (using KDE 4.0.1)
Installed from:    MS Windows Binaries
Compiler:          gcc.exe 
OS:                MS Windows

Adjusting the size of a synchronous message (on the bottom right and shown in the soon-to-be-attached pictures), causes the top Y position to change.

In the case provided, the top jumps up to the top of the canvas.  For other messages, the top seems to jump to a previous message.

.xmi and 2 screenshots attached.
Comment 1 Robert Lugg 2008-02-20 09:16:09 UTC 
Created attachment 23631 [details]
xmi file shown in the following two attachments
Comment 2 Robert Lugg 2008-02-20 09:17:58 UTC 
Created attachment 23632 [details]
message to resize is circled
Comment 3 Robert Lugg 2008-02-20 09:19:12 UTC 
Created attachment 23633 [details]
Dragging bottom down causes top of message to move.
Comment 4 Ralf Habacker 2015-03-08 09:52:22 UTC 

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