Bugzilla – Bug 9766
Alarms entered in reverse order
Last modified: 2008-12-15 12:24:28 UTC
When entering new alarms, SN/SC labels them in reverse order. Clear all alarms 1) Enter data for Alarm Clock 1 2) Enter data for Alarm Clock 2 (Notice that 1 is now 2) 3) Enter data for Alarm Clock 3 (Notice that 1 is now 3, 3 is now 1) Keep entering alarms, and you will notice they keep 'sliding' down the list, with the 'new' alarm always being the 1st alarm. If you enter your alarms by time, this will have the result of placing the alarms out of order. I.E. the earlier alarms will be last in the list, and the later alarms will be first on the list.
James - the order isn't reversed. It's ordered by alarm time. Whether that's as designed - who knows?
They're meant to be ordered by the order in which they were created. What interface are you using to create and display these alarms? Slim::Utils::Alarms::getAlarms returns a sorted list of alarms. It's up to the displaying interfaces to preserve this order and also to apply the correct name to them (this last bit is a bit broken, really). The name should be derived from 'ALARM_ALARM' + i, where is the count of the current alarm.
Will see what the issue is here.
Take a look at my SN account james_richardson@hotmail.com. Look at the BOOM I have attached Notice how the ALARMS are setup They were ENTERED earliest time (Alarm 3) first. My question is why do they NOT display in the order I entered them?
change 4956 - respect creation time when sorting alarms
Verified fixed in (sv) r5241/r24218
This bug has been fixed in the latest release of SqueezeNetwork! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.