Acknowledged
2 months ago
CIQQA-3139

onSettingsChanged() not fired for data field in simulator

In the SDK Ver 8.1.1 simulator, 

AppBase.onSettingsChanged() is not fired in a data field app when settings are changed from the settings menu (of the data field).
On an actual watch, it appears that the data field settings can only be edited when the data field is first added to an activity data screen.  When the activity is ALREADY RUNNING, the "Edit data field settings?" screen shows when the data field is selected but "Yes" cannot be selected.   The only way I can select Yes is when the activity is ALREADY RUNNING, is to remove the data field from the data screen then add it back, and when that is done I can select "Yes" and edit the settings.  
 
Is this the intended behavior?  If so, why can't settings be edited on the watch during the activity?
trudelta
Parents
  • 2 months ago

    > onDeviceSettingChanged (not exactly what you want)

    It's not what they want at all.

    It's obviously just a way to notify the app that one of the built-in device settings has changed (like 12h/24h time format or units).

    In the past, devs who wanted to respond to device settings changes in real time would have to call getDeviceSettings() constantly, and they'd have no way to know what fields changed. There were probably battery life concerns associated with this practice for many devs (I know I worried about it).

Comment
  • 2 months ago

    > onDeviceSettingChanged (not exactly what you want)

    It's not what they want at all.

    It's obviously just a way to notify the app that one of the built-in device settings has changed (like 12h/24h time format or units).

    In the past, devs who wanted to respond to device settings changes in real time would have to call getDeviceSettings() constantly, and they'd have no way to know what fields changed. There were probably battery life concerns associated with this practice for many devs (I know I worried about it).

Children
No Data