Reset Windows calls componentOpened a second time

[billooms]

I have a TopComponent in the editor mode. I generally add all my propertyChangeListeners in the componentOpened method and removePropertyChangeListeners in the componentClosed method.

The problem comes when a user does a "Windows" -> "Reset Windows". Something causes the componentOpened method to be called again so that now I get a second propertyChangeListener attached. When I fire a propertyChangeEvent, it gets handled twice (which is not what I want).

This only seems to be a problem with TopComponents in the editor mode. Another TopComponent in the properties mode will behave differently -- "Reset Windows" calls componentClosed first then componentOpened is called.

This is easily demonstrated:
Create a new NetBeans Platform Application
Add a module
Add a Window to the module in the editor mode and open on application start
Put print statements in the componentOpened and componentClosed methods (so that you can see when they are called).
Run the application -- you'll see that componentOpened was called when the program was launched. Then do a "Reset Windows" and you'll see that componentOpened was called again without having called componentClosed.

Is this a bug? Why should TopComponents in different modes behave differently with regard to "Reset Windows"?

How can I determine if there are already propertyChangeListeners attached to the TopComponent so that within the componentOpened method I can avoid attaching a second time?

I'm running on NetBeans 7.1 with all updates as of this writing, Mac OSX 10.6.8 (also with all latest updates) on a Mac Pro 2.66GHz Quad-Core Xeon. Java is 1.6.0_29-b11-402.jdk.

[Stanislav Aubrecht]

On 25.3.2012 22:05, billooms wrote:

[billooms]

Thanks for the feedback, Stan. I filed a Bug Report today.

It appears that this was reported a number of years ago (Bug 150151) and was resolved on 2008-12-12. It seems to have reared it's head again.

[Mvek]

And can someone confirm this bug: http://forums.netbeans.org/viewtopic.php?p=126519#126519 ? This might be related. I got problem while opening TC from TC in explorer mode, but without saying, where the new TC should be. It called componentOpened() after componentShowing(). Just moving the window while running the app. changed this behaviour.

[billooms]

Is sounds like a different bug. However you confirm by checking one of the latest builds. The bug I reported has been fixed on one of the nightly builds. see the bug report for details:

http://netbeans.org/bugzilla/show_bug.cgi?id=210380