Is there any sense of a light at the end of the tunnel on this bug? I'm still seeing it (v 5.2.1) and it's cause me to pretty much completely abandon SoapUI for Postman because SoapUI is useless to me with as tiny as the user interface is with this bug. I've tried a number of different solutions from around the web and all of them break the UI in some completely unuseable way.
Additional Info:
Laptop = Macbook Pro running Parallels
Screen resolution = 3840 x 2400 / 5120 x 2160
SoapUI version = 5.2.1 (64-bit)
OS = Windows 10 64-bit
Hi,
Have you tried what this guy did:
He was trying to use less than 4k resolution, but seemed to get around it.
Sorry if you have already tried this,
Regards,
Rupert
Hi,
I just tried what was suggested in that link on my Windows 10 64bit machine running at 4K, and it makes the text much better:
Does this not work running from within parallels?
Regards,
Rupert
Hi,
How is it possible that this still isn't fixed. Because of this I have avoided soapUI for half a year, but I really wanted to use it now. But no, still can't.
Like someone said above. High resolutions are here to stay. How long can smartbear ignore this?
Anyway back to postman, for now :mansad:
On Windows 10 Creator's Update on a Retina display 2880x1800, overriding the high DPI behavior, allowing the system to scale normalized the text size on both the Retina and when moved to a second 1920x1080 display.
Hi,
Is there any solution do this problem that works?
Have tried it all.
I also have the exakt same problem with VIM.
/Roniner
Thanks Rupert, This solution helped me to resolve the issue.
Regards,
Sivaganehsan
