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.
When I clicked save on the save icon, I got the above exception. (not often error, but once awhile).
Created attachment 12637 [details] The exception when save
It should have been some problem with activated nodes. I never experienced it. Closing as worksforme. If you experience it, please reopen, and try to put here the case, when it happened. It is important to know what windows were activated, what sources modified, etc.
Here's how to reproduce the error: Create a GUI form (Such as jpanel). Set to null layout and drop 3 or 4 components into it. Save everything. Next, go to the source tab, and enter 1 space but do not save. Next go to the form tab. Then click on one of the components you just droped into the form (wich was not selected before). What I expected at this point is the 2 save buttons on the tool bar (1 button is to save the file, while the 2nd button is to save all files) both enabled. Now, click on the 1st button once. This will make the 2nd button disabled, but the 1st button is still enabled somehow. Now, click on it again will pop up the exception (consistently).
Yes, I see, I can reproduce it too. Thanks. I'll look at it closer now.
It is a problem with RADComponentNode, passing to form where it belongs. I investigated following. Try this (like the original test case): 1) create form with Null Layout 2) put there two buttons 3) save all, button 1 is selected 4) switch to source, make some change (not connected to button sources, no-harmful one, just space) 5) switch back to form 6) now you can see the difference, when you switch between the buttons you see the action is enabled for the originaly unselected one and disabled for the originaly selected. That's wrong, it should be disabled for both I guess, anyway it should be same for both. I investigated more, and found out that lookup of those nodes (both RACCOmponentNode's) differs that for the one which is enabled it contain lookup delegating to editor support and for the second one not, thus the node claims at one moment is has save cookie. But when the cookie actually disappears, it probably doesn't fire appropriate change. Anyway it is needed to investigate in form, it is quite clumsy.
Should be fixed together with the issue 39982.
*** Issue 40062 has been marked as a duplicate of this issue. ***
Verified