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 46392 - Extra space in menu when using javax.swing.Action
Summary: Extra space in menu when using javax.swing.Action
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Actions (show other bugs)
Version: 4.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2004-07-21 13:50 UTC by jrojcek
Modified: 2008-12-22 14:53 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
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 jrojcek 2004-07-21 13:50:17 UTC 
Currently the Run Other submenu items contain transparent 
icons which makes an unnecessary empty gap.j Please remove 
the gap.
Comment 1 Petr Hrebejk 2004-07-21 14:23:45 UTC 
It seems that when using javax.swing.Action instead of SystemAction
the menu adds the extra speca automaticaly, even if the action has no
Icon.
Comment 2 Petr Hrebejk 2004-07-21 14:24:20 UTC 
Please evaluate
Comment 3 Jesse Glick 2004-07-21 18:47:18 UTC 
It's true that o.o.a.Actions.MenuBridge.updateButtonIcon forces there
to be an icon:

   button.setIcon(nonNullIcon(null));

I presume this is desirable in most circumstances since you do not
want menu items fully left-aligned when other items in the same menu
have icons. Not sure what, if any, fix is possible.

This is surely not P3. The gap is in fact consistent with other menus,
though useless in this case.
Comment 4 Jiri Rechtacek 2006-11-23 15:03:08 UTC 
Jano, is it still valid problem? Should be fixed? If not I'm going to close as
WONTFIX. Thanks
Comment 5 Jesse Glick 2006-11-23 22:42:55 UTC 
I don't see any extra spaces in a current dev build. Was this already fixed?

(WONTFIX should only be used for acknowledged bugs that you simply do not plan
to fix. If the issue existed but has since been fixed use FIXED. If you cannot
confirm that the issue ever existed use WORKSFORME. If the bug report is missing
information or just makes no sense use INVALID.)
Comment 6 jrojcek 2007-01-15 12:38:06 UTC 
I believe this issue existed, but it seems to be fixed now. So FIXED? :-)
Comment 7 Jiri Rechtacek 2007-01-15 12:44:05 UTC 
Per Jano's request closed as FIXED.