Complete
over 4 years ago

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
  • over 5 years ago

    Yesterday I played around with settings on my app quite a lot, and also I could see any problems as described here.

    Changes made in application (using Application.getApp().setProperty(key,value)) were always reflected correctly on App Settings Editor of Eclipse, and vice versa. Also Application Settings via 'View Memory" were always correct (of course need to restart it after every change, since it is only snapshot and not actively updating).

    This was on MacOS, your screenshot looks like PC, I wonder if there is difference on which platform this is run?

Comment
  • over 5 years ago

    Yesterday I played around with settings on my app quite a lot, and also I could see any problems as described here.

    Changes made in application (using Application.getApp().setProperty(key,value)) were always reflected correctly on App Settings Editor of Eclipse, and vice versa. Also Application Settings via 'View Memory" were always correct (of course need to restart it after every change, since it is only snapshot and not actively updating).

    This was on MacOS, your screenshot looks like PC, I wonder if there is difference on which platform this is run?

Children