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.
Summary: | Freeform Java Desktop projects, form designer unable to add @Actions defined in other classes to buttons/menus/etc | ||
---|---|---|---|
Product: | guibuilder | Reporter: | crusoe <crusoe> |
Component: | Binding | Assignee: | issues@guibuilder <issues> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | issues |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
crusoe
2008-05-17 00:14:29 UTC
Not quite sure where the problem may be, but it certainly does not look like a java/editor problem. The GUI builder currently does not support using actions from other classes (i.e. other than the form class itself and the application class). Note it is not that easy - you need an instance, not just a class, to be able to use the actions. Note there is already issue 130461 asking for support for actions from other classes. One possible approach is to allow to use all known instances in the form class to be sources of actions (i.e. scanning their classes for action methods and being able to set them). We could allow the user to specify any code expression for the instance and arbitrary name of action. This would be possible with the current version of Swing App Framework. There was also another idea - to use some kind of expressions to specify where the action method should be found without specifying the target instance directly (e.g. "someActionObject.myAction"). This could even combine actions with beans binding, but note sure how useful it could be. It would require changes in Swing App Framework, is more complicated, so unlikely to happen. *** This issue has been marked as a duplicate of 130461 *** |