AU: Desktop::setGlobalScaleFactor with value < 1 results in wrongly sized window

[CrushedPixel]

@ed95 can you have a look at this?
In this post, you recommend using Desktop::setGlobalScaleFactor over AudioProcessorEditor::setScaleFactor.

Indeed, on Windows (VST3) the former works and the latter doesn’t, but on macOS (AU) it’s the other way around - AudioProcessorEditor::setScaleFactor actually works fine but Desktop::setGlobalScaleFactor produces the issue above.

I want to release my plugin within the next few weeks, so it’d be good if this could be looked at!

Issue with AudioProcessorEditor::setScaleFactor

Since commit 18523101 the reccomended way to scale your editor is wrap it in a top-level component which you can apply a transform to or, if you aren’t concerned with having a different scale for each instance, to use Desktop::setGlobalScaleFactor(). The rationale for these changes is to improve the reliability of the DPI handling code on Windows as before when we were simply scaling the native HWND there were some issues with OpenGL plug-ins, multi-monitor support, and behaviour differences in …