Thank you, Lutz.

I understand there's a bumpy road ahead, but I think that we can track that particular change of condition (moving the application to a different monitor). What the application must do in response to that, well, that's the question. Even trickier, I think, is to control different top windows that may be displaying in different monitors.

Regarding VFPA: does it improve on the inclusion of a DPI-aware clause in a regular VFPSP2 application manifest?

>Hi Antonio,
>
>that's a goal. I know I'm failed decades ago with resizing on static DPI.
>
>Much fun. Small tip: Remember that one might move the whole VFP from a scaled to a non scaled screen. And if the UI elements do not follow this. Ouch.
>
>Until then, VFPA at least solves the problems with the reports. It's even not that bad with normal windows on scaled screens. Still problems with the frames on windows moved, but so far bearable :)
>
>
>>Dear All,
>>
>>By integrating a manifest into our executable applications, we know how to avoid the nasty effects of DPI scaling in modern Windows. Our screens won't be looking fuzzy, and our 9.0 reports will be displayed as designed.
>>
>>A manifest, however, solves only part of the problem. Our applications still render at 100% DPI scaling, and we're failing to honor the settings of choice of the users.
>>
>>I was thinking of adapting one of the available resizer class to (preferably automatically) adjust the size of forms and controls to the current display scaling. Instead of reacting to the windows' resizing, the target is to set the controls' dimensional and positional properties once the application instantiates a form.
>>
>>Even if I expect some challenging hurdles, like adjusting the menu system, I'm looking for recommendations on the resizer class of your preference. Or authoring! I don't mind a full code rewrite - in reality, I'm also expecting it - but I will welcome good, stable, and tested ideas, no matter their current form, together with a discussion and guidance on this topic.
>>
>>The result, if successful, will be available in open-source, with all due credits.