>Thank you, Christian. My remarks inline.
>
>>
>>The biggest challenge for me was scaling images, especially smaller icons on buttons etc. I am doing scaling based on 4 fixed settings (level 1 - 4) which the user can set as preference. The advantage of the fixed levels might be, that all objects on all forms have the same size, and the user sets this in one global setting which gets remembered per user and machine. It would be strange if the fontsizes changes throughout the application based on resizing individual forms. For the images I have 4 optimized versions for each level.
>>
>
>This is the actual scenario. There will be only a few scale levels depending on OS settings (as you reinforce below). The main difference is that there may be forms with different font sizes if they are placed in monitors with distinct DPI settings.
>
>You mean one optimized version of the images for each of the four levels, right? That's also what Microsoft suggests for icons, for instance.
>
>>Second challenge is dropping controls after form's instantiation, but with this approach I could manage it to apply the factor on later created objects. I typically would have container classes working as controls, so I don't need to drop and resize individual objects.
>>
>
>This is, as Lutz and Walter already warned, more difficult to integrate. At this points, I assume it will force rewriting our base classes and probably create Visible_assign events for the controls.

I'm not shure which way around, but one _ASSIGN or _ACCESS code fires on expected places. (IE ACCESS fires on ASSIGN or the opposite)
Check this, because this is all boring slow FoxCode that runs.
I would rather Eventbind to (each) CREATE~ or NEWOBJECT. This rarely fires. Newly created object is on top of ZORDER (iow, the last on Objects collection), so you can handle this directly after creation.