Are the components in this pack supposed to correctly respond to 4K monitors when DPI awareness Per Monitor V2 is used? We have a customer with a 4K display who is reporting incorrect scaling, most notably the RadioGroup component being reduced to very small text.
Is this something that needs to be reported as a bug, or is scaling for 4K monitors beyond the capability of the components? It's something we can work around if necessary, but just would like some guidance on what we should expect with the various DPI awareness settings. Thank you.
FNC is currently not High DPI aware, it is very high on our todolist and will look into it as soon as possible.
So it won't be compatible with the new HighDPI changes Embarcadero did in the new Delphi 11 Firemonkey?
We are working on it as we speak. We have awaited the new designtime requirements and found a lot of specific cases in which high DPI behaves differently, so we want to make sure that when integrating high DPI support in FNC it works both in designtime and runtime as well as backwards compatible with other IDEs. This will take a significant amount of time.
It is clear that it takes a lot of time. However, the "fact" is that TMS has simply neglected the issue for several years. (I'm thinking specifically of the FNCRibbon component).
Hence my question:
What is the time horizon? Will there be anything this year?
We are working on it as we speak. So you can expect high DPI improvements this year.