-
-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several problems with the GUI-behaviour on a two-screen setup #166
Comments
Thx for reporting. I can reproduce your 2nd problem. I have to open-and-close the "Save in" combobox 3 times until the popup list is at the correct location... strange... Regarding 1st problem: BTW are you using FlatLaf custom window decorations? If yes, does the 1st problem also occur if you disable FlatLaf custom window decorations? |
…o another screen with different scaling factor (issue #166)
@erl987 Found a problem when moving a window to another screen that uses different scale factor. Then the window did not stay at the mouse position. In my case it was placed about 500px below the mouse position, but still partly on second screen. Maybe this is the same problem as yours. Fixed in commit 0247308. Please try it and let me know whether 1st problem is gone. |
… another screen with different scaling factor (issue #166)
Thanks for the fast and helpful responses! The layout is like this: Scale factors: 250% / 125% ID: \Display0 (main) ID: \Display1 Actually yes, the problem only occurs if I need to check your recent fixes later today. |
The latest snapshot version of FlatLaf is indeed fixing issue no. 1, thank you very much! The problem with the open file dialog is still present though, please note that in our case it is actually only the opening dialog that makes problems and not the saving dialog. That is at least what I observe. |
…multiple screens with different scaling factors (issue #166) workaround for https://bugs.openjdk.java.net/browse/JDK-8224608
Turns out that 2nd issue is a bug in Java: https://bugs.openjdk.java.net/browse/JDK-8224608 It also occurs in other LaFs (Windows, Nimbus, Metal, etc) every time a heavy weight popup is used, which is the case when the popup does not fit into the window. E.g. large menus or comboboxes at the bottom of a window. You can try it with the FlatLaf 0.42 Demo (use Java 9 or later):
Now the popup is probably shown at wrong location. This usually happens only the first time after moving the dialog to another screen. So try moving dialog back to other screen and click combobox button... The reason that it occured in FlatLaf file chooser in you app is that comboboxes in FlatLaf show by default 15 lines, but in other LaFs only 8 lines. So other LaFs use a light weight popup because it fits into the dialog, but FlatLaf file chooser uses a heavy weight popup, which causes the issues. Anyway, after trying various workarounds and doing a lot of testing, I was finally able to fix it in commit ef4c467 😄 Fixed in FlatLaf 0.42 |
Yes, the file dialog is working well now for me! So all issues reported here are fixed. Thank you! /Ralf |
I have a primary 4k-screen on a laptop and a separate secondary Full-HD screen on Windows 10. The software is using Java OpenJDK 14.0.2. If using the
FlatLaf
L&F but not withMetal
for example, I get some weird issues:When I start our application on the primary screen and try to move it to the secondary (located to the right), the application partly moves over to the secondary screen but then suddenly jumps out of the screens to the left. Afterward, it is hard to bring it back to visibility, this works only via the keyboard.
When I finally have the application on the secondary screen, the File Open dialog is opening part of its components (the file-dropdown) on the primary screen.
These issues appear to be related to the
FlatLaf
layout, but also to the screen setup. Others don't have this problem with the same code.Do you have any suggestions on how to fix this? Is this a known issue? If necessary, I can try to create a small program that reproduces hopefully this issue at least on my computer.
Best regards,
Ralf
The text was updated successfully, but these errors were encountered: