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 101399 - Missing support for unlocking the locked-state when related locked-widget is removed from a scene
Summary: Missing support for unlocking the locked-state when related locked-widget is ...
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Graph (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@platform
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-17 16:00 UTC by David Kaspar
Modified: 2007-04-17 16:01 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Kaspar 2007-04-17 16:00:41 UTC 
The library is missing support for reseting the lockedAction state. This is
needed in case where a developer recreates whole scene meanwhile an user have an
action locked in the scene e.g. by holding left-mouse-button processed by
MoveAction.

The library should automatically trace the locked widget and in case the widget
is removed from the scene, it should unlock the locked widget and action. This
change is at implementation level and since it was not described in the
documentation it could be implemented immediately.

A problem is that an action may require to execute some additional
post-unlocking code. E.g. this is required to be implemented by ConnectAction
which has to remove the temporary ConnectionWidget from the scene. This can be
implemented by introducing a new factory method for locked state of widget-action:
WidgetAction.State WidgetAction.State.createLocked (lockedWidget, lockedAction,
unlockListener);
The unlockListener is going to contain "unlockNotify" method which would be
called at the moment when the scene forces to unlock the locked state.

I will attach the patch later. Then I will ask for fast-api-review.