Topic: 2 minor alarm behaviour changes
A couple of points about the 'alarms' functions on the Chumby if I may:
1. The 'one time alarm' currently, after having actually elapsed (ie: has been acted on) still appears in the 'alarms' list. I presume the reaon for this (in original reasoning of the logic of the Chumby alarms functions) was so that a user could subsequently return and 'edit' this alarm to a new date/time and make it active again.
I can't really see the point of this however. The number of keystrokes required to edit an alarm is basically the same as creating a new 'one time alarm' entry from scratch.
I suggest that a 'one time alarm' should automatically remove itself from the 'alarms' list after it has completed.
2. I recently had occassion to edit my alarms list. I selected an entry (a 'one time alarm' I no longer needed) and hit the delete key. Nothing happened, so I hit the delete key again - an act I shortly thereafter regretted.
I then discovered that my Chumby was momentarily 'busy' and had in fact recognised the first press of the delete key. Me having then pressed the delete jey again resulted in one of my 'daily' alarms also being deleted - and I then had to go through all the hastle of setting it back up again.
I suggest that the delete function on the 'alarms' screen be changed that 'permanent' alarms (ie: dialy/weekly/certain day of week alarms that you would not normally be deleting on a regular basis) be protected with a confirm screen - ie: a prompt asking 'are you sure' before they are actually deleted.