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.
Refuse multiplied borders, implement simple checking of TopComponent borders, add one if needed. Tabs and splitters generally will have no visually visible borders.
probable impl: class BorderPolisher will be hooked into ui.tabcontrol.ComponentContainer, which will call it upon add and remove component calls. BorderPolisher should be able to detect missing border and add one, and also restore original border when removing, as view can be in situations wehere extra border isn't needed (separate frame). Perhaps also identification of multiple borders is worthy.
moved to end of october.
issue enhanced to border management for all LFs, especially w2k classic and XP. Impl will be different that I thought: Special instance of BorderPolicy interface will exist for each LF, will be called from tab displayers to install proper border.
impl in progress now...
Basic border management implemented, here's what's left: - remove border from several components like form editor, editor - border policy for Metal LF - remove own borders from Win classic tabs.
all changed implemented and comitted. Huge amount of work btw, it was harder then I expected.