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 135251 - cannot move composite state element if grasp in body of element
Summary: cannot move composite state element if grasp in body of element
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram State (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Yang Su
URL:
Keywords:
Depends on:
Blocks: 138533
  Show dependency tree
 
Reported: 2008-05-16 23:28 UTC by Peter Lam
Modified: 2008-07-24 00:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lam 2008-05-16 23:28:17 UTC
build 20080516

Composite state element can't be moved if grasp in the body of the element instead of the name (tab) area.
Comment 1 Yang Su 2008-05-19 18:41:37 UTC
This is a change from 6.5 implementation. 

In previous releases, the region is not selectable, as the result, there is no visual feedback on selection, no separate
context menus, to delete a region user needs to select 'regions -> delete this region' instead of 'edit -> delete',
which could be confusing, exception occurs when invoking 'select in model'. 

To address those issues, I propose we make region ( a distinct model element ) selectable, so that it's highlighted when
it's selected and it can have its own context-aware menu items.

Making contained widget selectable implies changes to mouse action behavior. When mouse is pressed on region area, it
makes region selected first, while region is selected, trying to press mouse and drag it will make container widget ( in
this case, composite state widget ) move. Use can avoid this two-step action by dragging mouse on non-contained area, in
this case, state widget name area.

Suggestions are welcome.
Comment 2 Yang Su 2008-06-06 00:07:26 UTC
Decision has been made to switch to 6.1 UI behavior, region element will not have its own context menu, it will not be
selectable, region sub menu will be added to composite menu list. This issue will automatically go away after above changes.
Comment 3 George Vasick 2008-06-10 17:09:56 UTC
Removing obsolete assignments.  Bugs will be reassigned for M2.
Comment 4 Yang Su 2008-07-01 22:27:51 UTC
changeset e19b3aee11a6 in uml-main

reverted to use 6.1 design
Comment 5 Peter Lam 2008-07-24 00:50:27 UTC
verified in nb 6.5 trunk build 20080723145315