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.
Each TopComponent should be able to set its own properties. Editor.TopComponent.Closing.Enabled=false Splitter.Respect.MinimumSize.Enabled=false TopComponent.DragAndDrop.Enabled=false TopComponent.Maximization.Enabled=false TopComponent.Resizing.Enabled=false TopComponent.Sliding.Enabled=false TopComponent.Undocking.Enabled=false View.TopComponent.Closing.Enabled=false Chances are an application will have windows with some of the windows with all the properties enabled and some with a few enabled.Even if the majority of the applications will not use it. Lack of this feature only makes the API rigid as opposed to flexible. From my under standing the window system is centralized. i.e. the properties of all windows are being set by reading one Bundle.properties file located in branding module. A better approach would be to read the bundle.properties file from each topcomponent's module. Although this will assume that the same properties will be enabled for all the topcomponents in the same module, it is better flexibility than what we have now. Users might group the topcomponents with similar properties or they can create a class with specific properties by extending TopComponent and create instances of the class where ever they need.
*** This issue has been marked as a duplicate of 156453 ***