FWIW, the too-small scaling in the JUCE Plugin Host under Windows has been that way for as long as I can remember (I am set at 1.5x scaling on a MBP running Bootcamp)… I always thought the scaling was stuck at 1 logical pixel = 1 physical pixel, aka the JUCE Plugin Host is ignoring Windows’ DPI settings when displaying plugin windows, but the strange scaling in the JUCE plugin host with scaling factor 2 is making me think otherwise(?).
Scale factors have always been a bit of a car-crash on Windows and behave differently in different hosts, and on different versions of the OS… Although juce UIs are scalable, we’ve always tried to avoid attempting to dictate how devs want their plugin to work, because people have different preferences.
hi Jules - i can see this is a bit of a messy problem, but it’s not just Windows here - setGlobalScaleFactor doesn’t work on OSX either inside plugins. I guess the real answer is that setGlobalScaleFactor cannot be used in plugins and you need to go the AffineTransform route…
Yeah I had a look into this last month and my only real discovery was that AffineTransforms are hard and make my head hurt. I’ll add this to the backlog though and dive into it again when some of the larger JUCE 5 features are out of the way.
Hi @ed95, wondering if there’s any new information on the currently recommended way to handle high DPI on Windows. There’s not a lot of definitive information on the forum, and it seems all over the map in the hosts we’ve tested so far. Any suggestions would be much appreciated.