-
Notifications
You must be signed in to change notification settings - Fork 68
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
Support for HiDPI? #12
Comments
Hi, thanks for your bug report. I've split the crash issue into a seperate bug (see #13). Generally, if PRISM crashes hard (such as here with some segmentation fault in the native code), the Java runtime generates hs_err_pidXXX.log logfiles with details about the crash. As it seems that the 32bit version of PRISM works with JVM9 on Windows, it would be great if you could give that a try to see if switching to JVM9 solves the DPI issue. Note that you need a 32bit version of JVM9 as well... Otherwise, I can try to reproduce in a virtual machine. |
Ok, I ran the PRISM 4.3.1 GUI (32bit) on a VM with Window 10, JRE9 (32bit) and a resolution of 3268x1970. The GUI reacted to changes in the DPI setting of Windows (Display, "Change the size of text and other items: x%") on the fly. Using something like 175% or 200%, the GUI is quite usable, with reasonable font sizes. Some observations:
So, at the moment it looks like if you use HiDPI screens on Windows, you are limited to the 32bit version of PRISM, but that is usable with JDK9... When #13 is fixed, 64bit should also work. Some screenshots of the editor and the experiments plot view for 100%, 200% and 300%: 100%: |
I just installed 32bit Java9 and 32bit Prism and it looks good: menus and widgets are readable and accessible. |
We are trying to use PRISM on Windows laptops with HiDPI screens (with dpi settings greater or equal to 192dpi, resolution 3200x1800 and higher), but the text and widgets are unreadably small with JVM 8.
I believe this issue is systemic between JVM and Windows OS, so I tried Java 9 which implements JEP 263 (HiDPI support for Windows), but then PRISM does not start: it shows splash screen and exits shortly. It does not show any diagnostic information on the command line either.
Do you have any treatment to address HiDPI screens?
Is there a way to turn on more diagnostics? (I have modified xprism.bat to stay with current command line window, but it does not show anything)
The text was updated successfully, but these errors were encountered: