Editing alarms on "new model" seems to break something
|Target version:||2.0 Multiple models|
- Install application
- Connect, update currentmodel if mismatch
- Make new model, change name, click FrSky alarms
- modify alarms, and save
This will modify the new model's alarms as well as the CurrentModel's alarms
This ONLY applies when editing alarms on a "brand new" model. Probably because it uses currentModel if modelId == -1Solutions:
- we should get a model id before allowing the alarm edits.
- Prevent enabling of that button until model has a id (poor solution)
#2 Updated by Espen Solbu about 5 years ago
In onServiceConnected, we use the currentmodels alarmmap if we didn't have any alarms when we arrived here.
I think this is what is causing updates to alarm map to also modify current model
Needs to be changed to copy the alarms, reinitialize for this model, or prevent this state entirely (add alarms to model on creation)