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.
dev build 200110290100 IBM JDK 3.1 The PROPERTIES tab attached to the bottom of the explorer cannot be closed; it's missing the tab on the bottom which we can right-click on to close it.
There was fixed issue #14214 recently - when there is only one component the tab should be hidden. You can close the properties window, when it is undocked from the Explorer. To do this you have to select the properties window (i.e some tab in it) and then through menu Window, Undock View get the properties to the floating workspace and then close it. Agree that this isn't nice. There should be better way how to close the component - i.e. Close action in the menu Window. I am going to close this issue. Please, file an enhacement against window system to get this better solved - it will be good to start duscussion on nbui mailinglist about this enhancement. Thanks.
Changed issue to Enhancement.
Target milestone -> 3.3.1.
Target milestone -> 3.4
Reassigning to Jiri. Please evaluate, thanks.
Eval: There isn't any menu item (in a popup menu or the main menu) to close a docked component (except for docked to central). It is only UI question, it should be discussed on the nbui list. If there will be some menu item then the implementation will be very easy.
Actually this was discussed in the UI newsgroup over a month ago and people basically agreed it would be nice to add a small "X" in the top-right corner of the window.. Kinda like what Mozilla does for MDI frames. You might want to clarify some more with the UI people but this has already been discussed.
Similar enhancement for closing tabs is #15582.
This enhancement is very similar as issue 1558, it should be solved together.
Sorry for typo above. This enhancement is very similar as issue 15582, it should be solved together.
Needs to be figured out how to do that. Passing to UI.
Because Window System v1 will not be supported from now by our team, all old winsys issues (now "core/window system v1" issues) are going to be closed as WONTFIX. Changes in API which emerged both from UI spec and problems with adjusting to the older API are described in the document http://core.netbeans.org/windowsystem/changes.html. It shows also recommends how the client code should be adjusted to the new window system. If you think this issue apply also to the new winsys then change the subcomponent (to "core/window system") and REOPEN it.
issue doesn't apply to new window system - verified