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 200206100100, JDK1.4 fcs, MDI. Not 100% reproductable, but very probable on my computer: 1. Open a form. 2. Switch to "Editing" workspace and open the editor also there. 3. Switch back to "GUI editing" workspace. 3. Try to execute it (you are switched to "Editing" workspace, see Issue #24528). 4. Now, sometimes (~90% of cases for me), the size of (maximized) editor is not changed, and the output window is drawn above it. (See screenshot).
Created attachment 6173 [details] Screenshot of editor&output window
Can you try again. I am not able to reproduce it. There was some changes in default winsys settigns. Source Editor is opened with Welcome panel and is maximized by default.
Created attachment 6409 [details] 200206240100.
Created attachment 6410 [details] 200206240100(debugger).
200206240100 So, because the default execute workspace was changed to "None" performing the below steps is not succefull (the step 3 does not do what it is supposed to do). (But, you ought to not to wait so long for reproduction). There are two new steps bunches: (both): Step -1: Close all editors on all workspaces, including welcome screen. A) Changing default value of execute workspace: 0) Tools/Options/Debugging and Executing/Execution Settings/Workspace -> Editing (Please note that for default values, the problem is still here, changing this setting just makes it visible). follow the previous steps to reproduce. B) Not changing any default value, using debugging instead of executing: Perform the same steps as in original report, but instead of "Editing" workspace use "Debugging" and instead of "Execute" action use "Debug" action. It seems to me a bit less probable, but happens, as screenshot proves. I do not understand what difference make (possible) changing of default editor/welcome screen state. As you can see on the screenshots, the editor *is* maximized (that's why this annoys me, I can not see part of the code), and the welcome screen is closed.
It is problem of PerimeterLayout. The same cause as in issue #12668. Workaround is to either switch workspaces or restore/maximize internal frame to force inner desktop update. For more details look at issue #12668. *** This issue has been marked as a duplicate of 12668 ***
Resolved for 3.4.x or earlier, no new info since then -> verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.