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 200201090940), MDI, jdk1.3.1 & jdk1.4 1, start IDE with clear userdir 2, open some file (README from examples dir) 3, dock RUntime tab to Source Editor on left 4, maximize Editor 5, restart -> Runtime tab is really thin... some observations: -it's not reproducible in release330, or build 0101 -it's reproducible in 0701 -if step 4 (maximize) is skipped everything work fine -this happens only when restarting. Switching projects is fine.
I'm changing summary a bit... Just to be precise - this is not regression, this bug was previously hidden by another bug 19072 which prevented editor (or other frames) to stay maximized in MDI after restart. P2 doesn't mean regression here but pure fact that it is annoying for the users that their favourite layout is screwed up.
accepting...
Target milestone -> 3.4
Marek works on this issue.
Created attachment 4176 [details] patch19217.jar
I attached patch for main trunk. Lukas please test it.
patch tested, looks good, splited maximized windows are restored properly after restart.
Fixed in main trunk. Issue is fixed in main trunk. Fix is relatively complex so I would not recommend to put it to release33 branch (3.3.1). Issue causes incorrect restoration of maximized internal split frames. It can be for example Form Editor when maximized in MDI. Fix stores maximized bounds of mode to mode configuration xml (wsmode files). It also recomputes area bounds for MDI mode when frame is internal maximized. When configuration is saved area bounds are converted from maximized to normal, when configuration is loaded area bounds are converted from normal to maximized. Also wsmode dtd is modified. (Optional element "maximized-bounds" is added.)
Fixed in main trunk.
Waiver approved by QA.
I approve the waiver...
Waiver approved.
verified in main trunk, 200202110100
Complex and potentially risky fix. Requested to be waived for FFJ 4.0 (FFJ40_WAV).
Resolved for 3.4.x or earlier, no new info since then -> closing.