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.
Palette must not be a node-sensitive because it cause weird behavior while browsing nodes in the Explorer view (palette content is change according to each selected node in the Explorer). Instead of that, make palette to be document-sensitive, so the palette will show the content related to the active opened document in the editor. This also allows you to autoclose palette TopComponent whenever there is no PaletteConfiguration specified for the active document.
fixed the palette module listens to changes in the activated nodes and activated TopComponents. the palette window auto-opens when an editor that supports palette is opened or activated. the palette stays open until all palette-aware topcomponents are closed or hidden. the palette content changes when user switches input focus to another topcomponent. if the newly activated topcomponent does not support palette then the content for previously active window stays visible.
Will this scenario be handled: There is a editor topcomponent will three multiviews. Multiview1 has PaletteA in its lookup Multiview2 has PaletteB in its lookup Multiview3 has no palette. During swithcing between multiviews will the palette window content get updated. If the user swithces to Multiview3, what happens to the palette window. As per comment above: "if the newly activated topcomponent does not support palette then the content for previously active window stays visible." - User would not expect the palette of the previous multiview to be visible in this case.
palette window will close when MultiView3 gets activated.
Verified, Build 200507110943, JDK 1.6.0-ea