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.
We need the ability to mark/define a TopComponent as undockable. In different cases or categories of applications such as something used in early childhood development agencies or day cares where children are tested or analyzed it makes sense not to allow users to move certain things around. It is simply an issue of poor computer skills and usability. Sometimes it is important to not let the user have more than a certain amount of flexibility. One can always define a TopComponent to always open up in the same place, however, this isn't good sometimes because some users will accidentally drag a running instances components around on the screen then call a tech support line because they have no clue what just happened. The system needs to support the developer not allowing specific TopComponents to be undocked at all. I set this up as a P1 as the release of the undocking features will be with Netbeans 6.0. We can better support the developer with simple abilities such as this.
This one seems like a forgotten duplicate of issue 156693 fixed in 6.7M2. *** This issue has been marked as a duplicate of 156693 ***