On 10.12.2016 15:23, Ondrej Pokorny via Lazarus wrote:
On 10.12.2016 14:40, Michael W. Vogel via Lazarus wrote:
Oh, then we get a global switch to enable/disable high DPI support OS
independet (as defined in the Windows manifest - and then this value
has to take care about that switch).
Nono, these settings have to stay completely independent. As other
people wrote recently - they may have developed their own scaling
features - in that case they need DPI support ON in the manifest, but
built-in LCL DPI support OFF.
Imo, there's no need for big philosophy about this. Application.HiDPI :=
Off; should be enough for runtime (no need to store this property in
lpr/lfm or whatever, just put it after Application.Initialize). In
Lazarus options there should be: Enable hiDPI designing (can be true by
default if you want), so app design is done in old way and new
properties does not influence current projects just like that.
Some of us do not plan to switch imediatelly to hiDPI features (Michael
already mentioned why is it so), so global on/off is really needed.
zeljko
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus
