Complete

SDK 3.2 Application Settings no longer in synch with actual simulator settings

To replicate:

1. Start an app...

2. Use Application.getApp().setProperty(key,value); to set a property

3. Use Ctrl + M to verify setting is stored in ApplicationProperties

4. Restart the app 

5. Use Ctrl + M to verify setting is still stored in ApplicationProperties

6. Start Application Settings

ACTUAL BEHAVIOUR

7. Note that entire settings form has been reset to default values. It is not referring to current application properties at all.

EXPECTED BEHAVIOUR. 

 7. Application Settings should open with current values of application properties

9635560
Parents
  • in reply to jim_m_58

    Let's save you have a projected called Ver1, and you've be runnint it in the sim.

    In the sim's directory under apps, there will be Ver1.prg and under apps/setting, Ver1.set

    If you rename Ver1 to be Ver2, or copy Ver1 and have a Ver2, and then run that, under apps you'll have Ver1.prg and Ver2.prg, and under apps/settings, Ver1.set and Ver2.set.

    But here's the twist.  The prg files both have the same manifest ID.What can happen is that Ver1.set and Ver2.set get confused, as far as what's used by the sim and what's used by the app settings editor.

Comment
  • in reply to jim_m_58

    Let's save you have a projected called Ver1, and you've be runnint it in the sim.

    In the sim's directory under apps, there will be Ver1.prg and under apps/setting, Ver1.set

    If you rename Ver1 to be Ver2, or copy Ver1 and have a Ver2, and then run that, under apps you'll have Ver1.prg and Ver2.prg, and under apps/settings, Ver1.set and Ver2.set.

    But here's the twist.  The prg files both have the same manifest ID.What can happen is that Ver1.set and Ver2.set get confused, as far as what's used by the sim and what's used by the app settings editor.

Children
No Data