Appdeveloper: How to use Property_Manager

[stefan.erni]

Hi Ben

I tried to save properties, but no file was saved.
Not in the program folder or in the folder I specified.

[BenR]

Hi Stefan,

Thanks for letting us know I'm investigating for you now. It's also not saving for me either at the moment which is odd as we use this quite a bit in v10. hmm.

[BenR]

Right should be resolved now, I've cut out the sub components and now do the read/write directly and this seems to work much better and gives me much more control with what we are writing to the file so that's great and leads to less ambiguity with property values.

In your file you were using the string "InitialValue" but as this is a component property instead of a top level property this needs to be "RadioButton1::InitialValue"

I've fixed the tooltips for the RegisterProperty function so that this is also now more obvious.

Let me know how you get on.

[stefan.erni]

Hi Ben

Yes, when I export the app and run it, a config.cfg file is created. (Not with F5 debug.)
I can open and read the file, and make changes to it.
However, the value is not changed if i start again the App

Start with new config.

2026-01-15_10-24-03.PNG (58 KiB) Viewed 12 times

2026-01-15_10-07-29.PNG (42.25 KiB) Viewed 12 times

[BenR]

Hi Stefan,

This one is a bit tricky as the Initial Value sets the default value for the radio button at the start of simulation.

When you come to do the property load the simulation is already running.

What you could do is to add a start event macro to take the loaded value and then apply that to the radio button value.

Here's an example.

Property_Manager_Demo_drive_c.fcpcd

(12.01 KiB) Downloaded 3 times