-
Notifications
You must be signed in to change notification settings - Fork 7
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
Problem in running RuleBender on HiDPI screens #218
Comments
Hi @OleksiiR Can you try passing the argument to the RuleBender binary directly when you are running it? I tested passing the argument to RuleBender and it correctly recognized it on my end but I don't have a HiDPI screen to test the result. Best, |
Thank you for the reply. Yes, the argument passes, but it does nothing. Even if you do not have HiDPI screen, if this would work you would have seen bigger symbols in RuleBender. So, it must be passed in some other way. BTW, I found the advice here: https://wiki.archlinux.org/index.php/HiDPI#Java_applications Best regards, |
I'm taking a look at this now. As a side note, you can edit |
OK, you need to use e.g.
I don't think the Edit: I wouldn't copy paste the |
Hi @OleksiiR I'll take a look at the other issue in a second but did you ever resolve this? I haven't encountered this issue on my end and forgot to take another look after, sorry about it. |
Dear colleagues,
I have a problem in running RuleBender on a laptop with high resolution screen (high dots per inch, HiDPI). Everything related to RuleBender is very small and hardly readable. I found in internet that I have to pass -Dsun.java2d.uiScale=2 to the java virtual machine, but it is unclear how to do it, because RuleBender is a binary and not an edible script. The rest of java applications are scaled normally, because since since Java 9 the GDK_SCALE environment variable is used to scale applications, and only RuleBender uses java version "1.8.0_161".
Could you please help me to scale RuleBender?
OS: OpenSUSE 15.2
Desktop environment: KDE Plasma
Kind regards,
Oleksii Rukhlenko
The text was updated successfully, but these errors were encountered: