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.
Does not belong here, and may in fact cause problems for unit tests and headless mode in general. Suggest core/windows instead.
I agree. I wanted just test it, find possible problems and let people complain about performance or other possible problems. Dafe might have some comments about it.
Jesse, core/windows? I'm not strongly against, but how does the code relate to winsys as such? I think that there is *no* relation except from listening to main window (which is a hack anyway, will probably not work totally OK in separate window mode and could be done by listening on getAllFrames() instead). I can think of other possibilities - explorer code or utilities perhaps. Just clarification - in perfect world, fs should get notified from OS fs layer, update its model and fire changes to asociated listeners, is that right?
Not attached to core/windows as such; but it absolutely should not be in openide/masterfs, or anywhere in openide for that matter. Maybe core/ui would be appropriate. Re. push vs. pull model - yes, if Java supported that we would use it of course.
core/ui - why not ? Could I hook on main frame in some warmUp task ? Is there any problem with it ? Or is there better trigger ?
/cvs/core/ui/src/org/netbeans/core/ui/MenuWarmUpTask.javarevision: 1.6; previous revision: 1.5 /cvs/openide/masterfs/src/org/netbeans/modules/masterfs/MasterFileSystem.java new revision: 1.13; previous revision: 1.12 /cvs/openide/masterfs/src/org/netbeans/modules/masterfs/WindowsActivatedHandler.java new revision: delete; previous revision: 1.2