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.
In 3.3.2-RC2 (is that the same as 3.3.1 dev listed in "found in version" choices?), the location/state of the source editor window does not persist across sessions. It did in 3.3.1. steps to reproduce: - start off new session (new -userdir) - specify MDI mode - resize nb window to my liking (from nearly max to about 50% Windows desktop) - open java file (e.g. clockframe.java) - maximize source editor (via system icon in top right corner) - shut down NB - restart: source editor is not maximized as expected. It is same default size and orientation as initial instance. Actually, for a split second, I did see maximized source editor, but it immediately reverts to default small size (1/4 of NB empty "blue" space) I am using SDK 1.4, but also tried with 1.3. same result. Thanks Wendy
I am sorry but this is duplicate of issue 23836, thanks for report. *** This issue has been marked as a duplicate of 23836 ***
Marian, My report is related to but different than 23836 in one critical respect - I'm referring to document window behavior within the MDI desktop. 24466 refers to a regression seen in 3.3.2 from 3.3.1 for MDI IDE desktop Source Editor window state. Whereas 23836 is for remembering single frame state in 3.4. 3.4 works exactly as I expect for the steps I outlined above. 3.3.2 is broken IMO, but its released now and unless there is a 3.3.3, it probably doesn't matter much. Wendy
Steps to reproduce in issue 23836 describe only one way to reproduce bug. Both issues desribe the same scenario with different windows, but root of the problems (and fix) is the same: "Maximized state of windows doesn't persist after restart/switch projects " IMHO: issue 23836 I have filed against Forte For Java 4.0 - fcs and core contains the same code as NB 3.3.2 - fcs. Well, if I am not right reopen, please. Thanks. *** This issue has been marked as a duplicate of 23836 ***
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.
A CLOSED issue mistakenly moved into a NEW state... closing again (step 1).
x
*** This issue has been marked as a duplicate of 23836 ***
Closing again.