I received a request from a user who would like my plugin editor to be rescalable (on Windows and Mac).
Currently, the plugin size nicely follows the settings of the screen it’s on, in the sense that its size relative to the standard OS windows (such as Explorer or Finder) remains constant. Which is the normal expected behavior: you set the OS scaling up so that you can get enough screen estate with windows that are still nicely readable, and my plugin seems to currently follow that (even if you need to tweak some host settings a bit in some cases).
However, I can also understand that some people (like the requesting user) may also want to keep a 4K screen set to 100% scaling in order to get as much on the screen as possible (even if everything becomes pretty small then) and then want the plugin they’re working with to be larger while they’re tweaking parameters.
In order to do this, it would be needed to allow the user to rescale the plugin editor window the way he/she wants.
If doing it dynamically by dragging a corner/sizer is too error-prone, changing a preference with a few fixed possibilities in the plugin’s settings would be fine too (although that would be a bit more limiting, as it would affect all instances of the plugin, but hey, it could be a start…)
Currently, my plugin is bitmap-based (and I’m not going to change that now) so an actual rescaling of the pixels is the only option (yes, I realize it may look a bit blurry or pixelated then…)
I have now read several topics on the forum dating back to a few years ago (about fixed desktop scaling factor, an extra parent component with an affine transform, AudioProcessorEditor::setScaleFactor, etc…), but I think I got lost in all the possibilities and not sure what could actually still work today and what not…
So: what is the current advised way (for the latest 6.1.2 master release) to make it possible for a user to rescale the plugin editor window and its contents (including tooltips and combo/listboxes)?