nextgenhealthcare / connect

The swiss army knife of healthcare integration.
Other
868 stars 265 forks source link

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

Open chriseggroll opened 4 months ago

chriseggroll commented 4 months ago

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):

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

pacmano1 commented 4 months ago

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

There are other articles about it also.

chriseggroll commented 4 months ago

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 commented 4 months ago

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 commented 4 months ago

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 commented 4 months ago

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 commented 4 months ago

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