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 hosts. Using an AffineTransform for the editor smoothes out a lot of these problems but means that code that was previously using AudioProcessorEditor::setScaleFactor() will need to be updated to use one of the other scaling techniques mentioned. We’ve added an assertion in AudioProcessorEditor::editorResized() to catch this with an explanation, but if you’re running a release build then you may have missed this.
2 Likes