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.
Form editor is heavily using window groups. When form is selected, component palette and others are also shown. How this will be supported when one element will be form designer and second its editor?
Dusan, can you please update the UI spec in regard to this issue? I'm not sure how the windows are supposed to behave? thank you. please reassign back to me afterwards.
I discussed it with Tomas+Jano and I will add this issue into spec... Behavior should be following. When Form designer is visible (not necessary focused) in any View, then Component Palette and others should be also shown.
I've checked the current usage of TopComponentGroup. Currently form editor takes care of opening/closing the group (in FormEditorSupport). It check for the selected component and opens/closes the group accordingly. The MultiViewElement will get callbacks componentActivated/componentShowing which can be used to perform the equivalent of the current code. So the implementation of MultiViewElement for the form editor will be responsible for the group handling. Nothing is required on the API side. Tomas, any specific reason why the group handling is done as a listener in FormEditorSupport and as part of the FormDesigner topcomponent?
If also the MultiViewTopComponent when shown/hidden will delegate properly to selected MultiViewElement's methods, then this could work. In other words, componentShown and componentHidden methods must work reliably - i.e. always reflect the visibility state of the element on the screen - so we can handle the group visibility accordingly. But - I need to be able to go through all the form elements and check if some is visible - how can I do this? Now I just check if it is the selected component in the mode...
http://core.netbeans.org/source/browse/core/multiview/src/org/netbeans/core/multiview/Attic/MultiViewFactory.java?rev=1.1.2.5&content-type=text/x-cvsweb-markup&showattic=1 http://core.netbeans.org/source/browse/core/multiview/src/org/netbeans/core/multiview/Attic/MultiViewHandler.java?rev=1.1.2.2&content-type=text/x-cvsweb-markup&showattic=1 You can do the same as now, MultiViewFactory will give you a MultiViewHandler if the TopComponent passed in as parameter is a multiview component. With this handler you should be able to perform the required checks and tasks.
As the handler is to be provided by the framework and not designed to be subclassed (means in future you would like to add some methods there). It should be final class and not interface.
done. interface->final class.
This issue was solved long time ago. Because nobody has reopened it neither added comments, we are verifying/closing it now. If you are still able to reproduce the problem, please reopen. Thanks in advance.