You need the type attribute on the inner setting, but the value should not be the one of the possible values from the settingConfig but rather that of property. So for example instead of alphaNumeric it should be string:
Wellllllll I'm not sure this is a good idea any more. Or at least there's some place for improvement on Garmin's side.
I made all my changes (working on Fenix6 which has 32 KB DF memory), and then I tried it in the simulator on Fenix 3 (16 KB DF memory only), and it fails now with an Out of memory error. This could of course be because of my code changes, however the problem is that the call:
MyApp.getProperty(key_to_the_array_property)
uses 4K of memory, even when the return value is null. This is causing the problem... (At the beginning I thought that the returned Array<Dictionary> is too big, but no...)
Having array settings is good probably from the end-user's point of view, because the app settings is clearer, but if this is the price, then thanks not :(
ok, strange, perhaps wait until it gets a little more reliable. I did get it to work in the simulator. But when I then tested it, as beta, om my device (Edge 830) the array settings didn't save. I could add items on the phone, but after save and then entering edit again it was blank...
