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.
Window system in the last continuous build behaves strange. Windows are open "maximized" in IDE and when you try to close a window it freezes IDE (see attached thread dump). To reproduce: - from main menu open Execution window (Window -> Execution) => it is not shown until you resize the main window. Then it fills all displayable area of the main window (except menu bar and tool bar) - try to close Execution window using the cross button at the top right corner => IDE freezes. When you resize the main window, it shows the welcome screen. Tested in build 20040301-1056, JDK1.4.2_03, WindowsXP.
Created attachment 13746 [details] Thread dump
*** Issue 40636 has been marked as a duplicate of this issue. ***
It must be fixed before HR !
Possibly related to some changes I did last night. Principally these were removing extra validations of the main window during startup, which caused it to flash, lay itself out multiple times, etc. But why would the continuous build only start failing now, 12 hours after committing these changes? FYI, the main window is not frozen after you close the execution window - it is just not re- laid out. If you resize the main window, will lay itself out and work again.
Tim, please fix asap
Tim is right, main window isn't repainted - "only" another test case : - run IDE - close Welcome, Runtime - try to close Filesystems -> Filesystems tab stays visible - resize main window -> whole main window is repainted - it's ok now
I didn't say the last continuous build started to failing. I just found it in the latest build.
Created attachment 13748 [details] Diff of all validation related changes from last night
Okay. Very simple fix is to put back: invalidate(); validate(); repaint(); in MainWindow.setDesktop(). I tried doing it a couple other places to make it cleaner, but without complete success. I would prefer to have some time to really figure out what is wrong - whenever you see code like this, it usually means the developer is flailing around trying to find something that works, found something and left it that way. Adding a component to the hierarchy should auto-magically trigger a layout if needed, of those components that are actually affected - an explicit call to validate() usually means something is wrong somewhere else. At the same time, probably I won't be able to review how layout and preferred size and such are handled through all the components in the winsys between now and 7PM. I'll poke at it for another 15 or 20 minutes, and if I don't have a better solution, put it back the way it was. But this should be fixed properly later.
it may be easier to just first revert the last commit and then spend time to fix it properly, not under pressure. Note this is P1
Fixed, the old code is back. Checking in MainWindow.java; /cvs/core/windows/src/org/netbeans/core/windows/view/ui/MainWindow.java,v <-- MainWindow.java new revision: 1.22; previous revision: 1.21 done
verified in [nb_dev](200403011900)