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 223026 - Need ability to detect current moving widget
Summary: Need ability to detect current moving widget
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Graph (show other bugs)
Version: 7.2.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: issues@platform
Depends on:
Reported: 2012-11-30 07:07 UTC by _ wadechandler
Modified: 2012-11-30 07:18 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description _ wadechandler 2012-11-30 07:07:03 UTC
Need a way in the Visual API to determine the currently moving Widget. Currently the MoveAction has the movingWidget held in its state. This is private currently. Seems this could be reflected in the Scene object in some way. The currently moving Widget for instance. Maybe some how one can move more than one thing at a time in the scene if they select more than one thing. So, perhaps it would be a list. Could even be that the ObjectState is updated with a new property to reflect this. Perhaps both could be done.

Either way, at the moment I need to detect the currently moving Widget in SceneListener so I can rearrange after validated all but the one which is moving when validating is called. Right now, the only way I know how to do this is to do what the default MoveProvider does. Even that is difficult though since one can not access the default MoveProvider. They can only look at the sources and mimic that as there is no way to get an instance of the default one outside of the APIs. Were one to be able to do that, and what it does clearly documented, then they could proxy to it and only override what they need.
Comment 1 _ wadechandler 2012-11-30 07:18:39 UTC
I think in my case, current case anyways, I can figure out the moving Widget since I'm using a SceneListener. This because it should be outside the current preferred location and bounds with the scene insets since I'm using validating and the validated method and considering the way Scene will be changing size and what I will be specifically looking for. My needs are after the fact and only required if the scene actually changed size. Other than that I don't care in my current use case. However, if someone needed to know more specific information it seems the only way is with the MoveProvider to set specifically the "moving" widget in some shared context.