SOAP UI 5.0 DPIAware

[ver0n]

when I start Soap UI 5.0 under win 8.1 with my 3200*1600 Notebook, Soap UI seems to wrongly declares to be DPI aware, and displays too small on my high DPI screen.

when I configure Soap UI in Win 8.1 to run with "Disable display scaling on high DPI settings" then some parts of SoapUI are looking even bigger.

Therefore I asume, that SoapUI pretends to be DPIAware, but does not really scane up itself.

Does anyone have an idea? I was wondering why nobody have the same issue with SoapUI.

[vcas4128]

I have exactily the same issue on windows 8.1 with SOAPUI 5.1.2.

[NiclasReimertz]

Are you getting this in Ready! API as well?

/niclas

[arktic17]

I also do have the same issue with SoapUI 5.1.2

I do not use Ready ! API so I can't tell you about it.

I hope you can save our eyes 🙂

[vcas4128]

Up

I have exactily the same issue on windows 8.1 with SOAPUI 5.2.1

[yaplex]

It's same for me, Windows 10x64, 3200x1800 (15 inches) monitor, SoapUI 5.2.1

when application starts, I see SoapUI logo, and logo looks scaled well, but as soon as actual application starts, it's very small, unreadable.

[user]

I got scaling issues as well. It's very very small. Basically unreadable.

Windows 10x64

3840 x 2160 (15 inch)

SoapUI 5.2.1

[Mediamana]

Hi guys

I was also bothered with high dpi issues with my UHD laptop on Windows 8.1 but found a solution ( tested on eclipse and soapui but probably also with all exe).

First add a registry key (long time since i haven't launched regedit lol)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest (DWORD) to 1

Then add a manifest file next to your exe

SoapUI-5.2.1.exe.manifest

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
    <description>eclipse</description>
    <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
        <security>
            <requestedPrivileges>
                <requestedExecutionLevel xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3"
                               level="asInvoker"
                               ms_asmv3:uiAccess="false">
                </requestedExecutionLevel>
            </requestedPrivileges>
        </security>
    </trustInfo>
    <asmv3:application>
        <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
            <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</ms_windowsSettings:dpiAware>
        </asmv3:windowsSettings>
    </asmv3:application>
</assembly>

Hope that helps, it changed my life 😉

[johncaruso]

I can confirm this issue remains in both SoapUI and Ready! API under Windows 10 x64 on a HiDPI laptop (3200x1800 - Lenovo Yoga 2 Pro).

[maowens]

I tried your fix to no avail, yet I do want to ask you a question for clarification.  You state to create a new key. Are you saying create the KEY PreferExternalManifest, did you mean create a DWORD of that name and if not what is the name of your DWORD.

The manifest that you created is there any modifications required or is that file generic enough to be used anywhere.

Thanks