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.
I have one component used at two places: in a wizard and as a customizer. I cannot use as such because the CustomizeAction improperly creates container that does not follow standard UI rules (ie. 12,12,12,11 margins). Wizard provides correct container with borders set. To WORKAROUND it I must create two components one used for customizer (with borders managed by the component) and one for the wizard (without borders, they are managed by container). One approach - container managed borders (it is prefered, is not it?) - component managed borders should be used consistently. The rule should be added to guidelines.
Eval: It's easy to change customize action to put border around customizer component, however it will need modifications from people which supply own customizers with borders already included.
fixed in main trunk, customizers are now surrounded by default empty border.
I rollback the change made b/w 1.83 and 1.84 in core/src/org/netbeans/core/NbNodeOperation.java because it requires modifications in all existing customizers which until now are hand-tuned to match the zero margin. We don't have enough time to redo all customizers for 3.4. Feature freeze is behind the door.
ok, as you want Trung, moving target to 4.0
NbNodeOperation.java new revision: 1.86 contains workaround for XML module #21547.
Postponing to 4.0. Issue should be solved early in the release cycle in following way: - renew existing patch to NbNodeOp - make patches for existing customizers, post on nbdev etc to notify possibly affected module owners - integrate all patches together
Assigned to new owner.
Is it still valid task? Is somebody affected by this? Can I close as WONTFIX? I really don't plan to solve before long.
Yes, it persists. Workarounds are still in place.
No current nor future plans to solve this problem. Closed as WONTFIX.