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.
Models.ActionPerformer + createAction() are not that flexible. Their main purpose is to help map ActionEvent's to debugger objects/nodes. This is performed by the internal-Node->object map in ActionSupport. The problem is that if you want a slightly more sophisticated action, like a BooleanStateAction, you're stuck. So why not make the service that ActionSupport performs be explicit and have a method, getActionObjects() that uses getActivatedNodes() maps them to the debugger objects and returns those objects.
Ivan, can you please elaborate? Why is not the current state sufficient and what BooleanStateAction are you talking about? The ActionSupport calls perform() of the target performer on the debugger objects. That should be sufficient for the performer IMO.
Still incomplete => wontfix.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.