With an FMX application, which also contains only one button and one edit field, the result looks correct (same test conditions)
It would be good if the status name can be set manually. State 1, State 2 is not self-speaking and since there is no confirmation prompt, the layout is overwritten very quickly.
Additional notes:
When trying to use an HD monitor with 100% scaling, the arrangement of the VCL components works. If the scaling is set to 150%, the arrangement of the components does not work correctly.
Thank you very much for the feedback! The first version of the BETA unfortunately does not yet take high DPI into account. This will be worked on next week and your test application will help with that. We'll make sure to update the BETA when we have high DPI working! Thanks
This can be done by editing the Name property in the States collection editor
Before overwriting an existing state it would be useful to introduce a security query ("do you really want to overwrite")
The first version of the BETA unfortunately does not yet take high DPI into account.
It affects not only High DPI, but the scaling if it differs from 100%
(In a later test I tested with a HD monitor with a scaling of 150% - see post #2).
En tiempo de diseño el load settings no esta cargando bien los estados y uso save settings para salvar el archivo tms.rsettings. para usarlo en tiempo de ejecución al caer el formulario.
Unfortunately, it's unclear exactly what you mean. Spanish is unfortunately not our native language. Is it possible to bundle all feedback in English with step-by-step instructions?
I have not been able to detect any errors with different scaling at the moment.
However, I have noticed one small thing:
Create a new project
Add edit field, button and the component "TMSFNCResponsiveManager
create first state
resize the window and rearrange the components
save the state and then start the program
Result:
The component does't work, the current display remains.
For it to work, I need to change the state after saving the new state (state 2 -> state 1) and only then the program will work properly. This applies to VCL and FMX.