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.

Bug 123659

Summary:	Window positions are reset upon shutdown&startup
Product:	platform	Reporter:	jayllo <jayllo>
Component:	Window System	Assignee:	David Simonek <dsimonek>
Status:	RESOLVED WONTFIX
Severity:	blocker	Keywords:	DUAL_MONITOR
Priority:	P4
Version:	6.x
Hardware:	PC
OS:	Windows XP
Issue Type:	DEFECT	Exception Reporter:

Description jayllo 2007-12-07 21:51:01 UTC

I have a 3 monitor setup, I drag various window components such as the navigator box, or palette from the main ide frame
such that they form their own frame (existing in a separate jframe) on another monitor (so if the netbeans ide is on
monitor B, and I created two separate frames on A & C) upon shutdown of the IDE then startup, all the jframes are
recreated but their positions all end up on monitors A & B, none end up on C. In essence the original positions of the
jframes are not respected.

I also have to say, maximizing a jframe takes several seconds and causes the IDE to lock up. If you could fix that
performance issue everything would be golden. 

Thanks.

Comment 1 jayllo 2007-12-09 00:09:00 UTC

I have to add, with some more experimentation the dependent components that show up also have their window positions
reset, just by toggling between say a JSP & a java file (the palette will reappear in the netbeans monitor unless
anchored to a jframe that has a component which is not changing, such as navigator).

Comment 2 Lukas Hasik 2008-02-07 14:43:41 UTC

uff, uff, decreasing priority to P4. It seems as real corner case for me. 
I'd like to see a picture of your work enviroment ;)

thank you for report

Comment 3 Quality Engineering 2009-12-21 06:50:16 UTC

This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team