Between b74ae26eeefb and 38ea4c96b37b, using this flag produces:
java.lang.AssertionError: Must run in AWT queue.
and the IDE exits.
BTW this flag's main purpose is to avoid wasting a bunch of vertical screen space on a status line which is usually
empty and even when not empty can usually fit comfortably into the otherwise blank area to the right of the menus. In
practice this translates to an extra line or two of editor text, which is significant on a laptop.
caused by jarda's fix of #30121
Created attachment 78154 [details]
I would fix this using the above patch. Imho it is safe to construct components outside of AWT before the main window
is shown. But I'd rather let it for Standa to accept or reject this change.
Last I remember, making AWT comps outside of EQ is never safe, even if no window has yet been shown.
well, very recently i was fixing a couple of deadlocks because swing components were created/accessed outside AWT thread.
can't we create the main window in AWT thread?
alright, go ahead and integrate the patch. if the main window isn't visible yet then the risk is low
Integrated into 'main-golden', will be available in build *200903181604* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jaroslav Tulach <email@example.com>
Log: #159930: Integrating patch as S. Aubrecht suggested. Mainwindow can be created outside of AWT initially.