Skip to content
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

[BUG] Mirth Administrator DPI Scaling Issues After Installing 4.5.0 #6096

Open
chriseggroll opened this issue Feb 9, 2024 · 6 comments
Open
Labels
bug Something isn't working

Comments

@chriseggroll
Copy link

chriseggroll commented Feb 9, 2024

Describe the bug
After upgrading to 4.5.0, the Windows 10 Mirth Administrator text is very small and hard to read. I performed the steps outlined here but did not resolve the issue.

To Reproduce

  1. Launch Mirth Administrator Launcher
  2. Launch my local running service (added extra options to mcservice.vmoptions per the document here
  3. Login box appears and is scaled appropriately
  4. After entering credentials, the box becomes smaller during the step loading extensions
  5. Mirth Administrator Launcher text is too small.

Expected behavior
Mirth Administrator Launcher should use my DPI Scaling settings.

Actual behavior
Mirth Administrator Launcher is using the native resolution text size instead

Screenshots

At first, the login box is scaled appropriately
image

When it gets to the "Loading extensions" step, the box gets small
image

When the Administrator Launcher appears, the text is small
image

I did the following step on java.exe and javaw.exe

image

Environment (please complete the following information):

  • OS: Windows 10
  • Java Distribution/Version: Java 17 Bundled with the Administrator Launcher
  • Connect Version: 4.5.0

Workaround(s)
setting the DPI scaling for the mirth administrator launcher executable, launcher.exe seems to be the workaround.
manually changing the dpi scaling from display settings with the mirth administrator open also works, but only while the administrator is open.

Additional context
I upgraded from 4.4.2 to 4.5.0

@chriseggroll chriseggroll added the bug Something isn't working label Feb 9, 2024
@pacmano1
Copy link
Collaborator

pacmano1 commented Feb 9, 2024

@chriseggroll
Copy link
Author

https://forums.mirthproject.io/forum/mirth-connect/support/15397-mirth-and-4k-monitors?p=100598#post100598

There are other articles about it also.

I tried this fix even though it is several years old and I have been using the same monitor without problems for years, but sadly it did not resolve my issue, and the same thing I described above happens. I added the registry key, created the manifest files, restarted, and then tried. I have not run into this problem until upgrading from 4.4.2 to 4.5.0

@chriseggroll
Copy link
Author

I did find a workaround - changing the DPI scaling while the administrator is open re-scales it, but the same thing happens when it is closed and re-launched. At least now I can see what I'm doing

@pacmano1
Copy link
Collaborator

pacmano1 commented Feb 9, 2024

I'll ask to ask - where do you put those files? Mirth Admin Launcher can use its own bunlded JRE 8, 17 or you tell it to use your installed version.

@chriseggroll
Copy link
Author

I'll ask to ask - where do you put those files? Mirth Admin Launcher can use its own bunlded JRE 8, 17 or you tell it to use your installed version.

I put them in the folder for the bundled java 17: C:\Program Files\Mirth Connect Administrator Launcher\jre\bin

What worked for me and I thought I had already added another comment, is setting the DPI scaling for the mirth administrator launcher executable, launcher.exe, found the suggestion in this thread

@pacmano1
Copy link
Collaborator

pacmano1 commented Feb 9, 2024

Maybe edit your orginal bug post with the workaround where it says "None".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants