This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 153237 - Combined fragments should know what they contain
Summary: Combined fragments should know what they contain
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Sequence (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-14 17:54 UTC by thomasmatzner
Modified: 2008-11-14 19:09 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thomasmatzner 2008-11-14 17:54:25 UTC
When entering combined fragments into an activity diagram, they are treated just as rectangles that can freely flow
across the diagram. This leads to the following complications:

- Fragments may overlap each other.

- When editing the messages, some of them are likely to move up or down in the diagram, leaving the fragment or fragment
operand they belonged to. The only way to fix this is checking each message manually to find out whether it's still in
the right fragment.

- When inserting messages somewhere in the middle, all fragments the message is enclosed in have to be resized manually
to make space for the additional message.

- It is left to chance whether the left and right margin of each fragment covers all messages contained in it.

Suggestion for improvement:

- Each fragment should build up a static connection to all lifelines contained in it.

- There should be two ways of moving lifelines. One would make sure that the lifeline stays in the fragments it is
contained in, possibly by enlarging the fragment and moving the fragments in the neighborhood. The other one (possibly
pressing Ctrl while moving the line) would freely move the line without maintaining the lifeline/fragment relationship.

- A similar mechanism should hold for nesting fragments. Re-sizing a fragment (manually or by the mechanism described in
the previous paragraph) should resize all fragments containing it, and possibly move the fragments in the neighborhood,
as to maintain a proper nesting of fragments.

- The left and right margin of fragments should not be editable but be determined by the leftmost and rightmost lifeline.
Comment 1 Sergey Petrov 2008-11-14 19:09:31 UTC
there two issues already on cf behavior to support better integration with messages.
as for overlapping it's also possible for packages (for example) even it have no modeling sense.