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.
Build: NetBeans IDE 6.8 (Build 200912041610) VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_04-b12 OS: Windows XP, 5.1, x86 User Comments: mgoe: Starting Netbeans 6.8beta. GUEST: Initiation of Netbeans. Opening projects Maximum slowness yet reported was 18016 ms, average is 9253
Created attachment 92755 [details] nps snapshot
Change of default owner.
Making MainProjectAction enablement run off EQ seems easy enough, but then this would seem to contradict work done in bug #163201 which I do not really follow the purpose of.
Created attachment 97131 [details] Patch to avoid blocking EQ
I don't think there is any contradiction. Your patch just performs computation of the state outside of EQ and later notifies the change in EQ. The bug 163201 does the same as far as I can tell. Feel free to apply.
In order for your test to pass I needed to delete assertTrue("Need to be called from AWT thread", EventQueue.isDispatchThread()); and I was not sure what the purpose of this assertion was; the point of my patch is precisely to _not_ call these methods from EQ.
Feel free to remove the asserts in the test. I made them to verify that the MainProjectAction delays its initialization until it is first queried, that it does not eagerly compute something while created (outside of AWT thread). Probably even better is to keep the asserts on while run.init(); is called, but disable them when EventQueue.invokeAndWait(run) that might correctly capture my old and your new intention.
core-main #9b32aff251d0
*** Bug 186231 has been marked as a duplicate of this bug. ***
Integrated into 'main-golden', will be available in build *201005182201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/ User: Log: