LiveCode Forums.

Jacque thank you for your reply and explanation.
I think I begin to understand the difference between save stacks and save datas.
For my application I create a satck with a choice of languages​​, an English and a French button.
Changing the language in the fields is done by the custom properties that are in the Stack property inspector (see image)
And it is this choice that I'd like to save when I quit and relaunch the application.

Concerning the savings of stacks, I added in the PreOpenStack:
"wait 5 milliseconds with messages" after "save temp"
and now it's working.
but I'm not sure if this is the best solution
Best regards
Boris

Hi Jacque,
Thank you for explanation
I never used stack to save data.

Boris,
Yes, I can help you and you can help me

Best regards

Jean-Marc

sirobchGA0cda wrote: Concerning the savings of stacks, I added in the PreOpenStack:
"wait 5 milliseconds with messages" after "save temp"
and now it's working.
but I'm not sure if this is the best solution
Best regards
Boris

I don't think waiting 5 milliseconds will fix the duplicate card issue. But you are right that saving only the custom properties is a much better way to do it. You can continue to use your data stack. The script should check to see if the data stack already has those properties. If not, you do not want to load them into the main stack because then the main stack properties will be empty. If the data stack does have the properties then the script should go ahead and load them. When the main stack closes, it should write the properties to the data stack always.

To load the properties from the data stack:
To update the data stack when the main stack closes:
See if you can figure out how the handlers should be written. Remember to check for empty properties in the data stack before using them on launch.

Thank you Jacque for your answer.
I will tested with your proposition.
Boris