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.
Currently winsys is saved when project is closed. Architectural intent was to persist the IDE state on disk imediately. Parts of IDE already do this (e.g. settings, filesystems). This was filed accordnig to RFE originaly filed agianst the projects module (see issue #15191).
CCing reporter of original RFE.
Target milestone -> 3.3.1.
Target milestone -> 3.4
Reassigning to Marek. Marek, please evaluate these enhancements, thanks.
Due to performance we cannot save window system immediately. Some compromise must be implemented not to degrade IDE performance. It also means adding flags to detect changes, We must always save some block eg. mode configuration must be stored. We cannot just save one value because we store whole xml file as text. Also we must ignore events originating from our own saving (perhaps using id in atomic section?). Complex.
deferring for 4.0, this doesn't seem too important to me.
*** Issue 21020 has been marked as a duplicate of this issue. ***
Given that I don't understand the implementation details for this fix, I disagree that this should be deferred to 4.0 based on it's importance. This is issue is vitally important to the performance of the IDE to those that are extending NetBeans. Because of #22599 bug's dependence on this issue, the ever-increasing memory footprint affects performance to the point of throwing OutOfMemoryExceptions. How could that not be important!
As I fixed issue #22599 I implemented partially this task but this partial solution has some saving code in winsys classes - it should be moved to layers classes in final solution. Change login (detection of change) should stay in winsys classes with property/components granularity given by xml configuration files granularity.
*** Issue 26476 has been marked as a duplicate of this issue. ***
Because Window System v1 will not be supported from now by our team, all old winsys issues (now "core/window system v1" issues) are going to be closed as WONTFIX. Changes in API which emerged both from UI spec and problems with adjusting to the older API are described in the document http://core.netbeans.org/windowsystem/changes.html. It shows also recommends how the client code should be adjusted to the new window system. If you think this issue apply also to the new winsys then change the subcomponent (to "core/window system") and REOPEN it.
issue doesn't apply to new window system - verified
This issue had *1 votes* before move to platform component