-
Bug
-
Resolution: Fixed
-
P3
-
1.4.0
-
b27
-
generic
-
generic
-
Verified
Window.setLocationRelativeTo() does not work properly for virtual screen setups. This method calculates incorrect locations for a vertical virtual screen setup where the Y value of one of the screen bounds is non-zero. When comparing whether the newly calcuated Y location + window.height exceeds the max screen height, it does not take into account the Y value of the screen. On a vertical virtual screen setup, this Y value will be non-zero and location of any window is with respect to the entire virtual space. It must add the 'Y' value of the screen to the height of the screen as given in the suggested fix column.
This is noticed on Win32 as well as unix + xinerama with a virtual screen having 2 screens placed vertically. Reproducible since 1.4. (More detailed config details are given under comments)
I have attached a sample test. Execute the sample test on a vertical virtual screen setup. Move the frame to the bottom of the bottommost screen and click the button. You will see a window appearing on the primary monitor.
###@###.### 2004-12-22 13:36:27 GMT
This is noticed on Win32 as well as unix + xinerama with a virtual screen having 2 screens placed vertically. Reproducible since 1.4. (More detailed config details are given under comments)
I have attached a sample test. Execute the sample test on a vertical virtual screen setup. Move the frame to the bottom of the bottommost screen and click the button. You will see a window appearing on the primary monitor.
###@###.### 2004-12-22 13:36:27 GMT
- relates to
-
JDK-6177452 setLocationRelativeTo() places the window incorrectly on multi-mon-xinerama when comp is invisible
-
- Closed
-
-
JDK-5096679 PIT:PrintDialog is not positioned properly on multi-mon, when coords are invalid
-
- Closed
-
-
JDK-6232687 Window.SetLocationRelativeTo: treat the given null and invisible component separately
-
- Closed
-