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.
If the user does not specify an icon for the action, it should generate putValue("noIconInMenu", Boolean.TRUE); in the constructor (or, better, initialize() method).
Probably better to get rid of inititialize comment at all in callableSystemAction.javx and put it into the constructor to make it easiest to understand for the user. If not, we should do the same for both action. Since currently for callableSystemAction.javx we always generate: // protected void initialize() { // super.initialize(); // } Probably to show the user that something like this exists. However for cookieAction.javx never. So should I: 1) keep initialize method (sometimes just comment) always generated (for both types of actions)? 2) should I generate putValue into the constructor or initialize. Maybe the former is less confusing.... not sure? If there is not strong opinion I'll generate(conditionally) putValue into the constructor and get rid of initialize method/comment at all. Huh, little messy, but I hope understandable :)
Prefer usage of overridden initialize() method (w/ call to super) to overt constructor whenever using any SharedClassObject subclass. Ensures correct behavior in case original instance is GC'd and a new instance is created later (not sure if this can happen for SystemAction's, but just in case).
Fixed. Checking in ui/wizard/action/DataModel.java; 1.11 --> 1.12 Checking in ui/wizard/action/callableSystemAction.javx; 1.4 --> 1.5 Checking in ui/wizard/action/cookieAction.javx; 1.6 --> 1.7
verified