Bugzilla – Bug 9510
Allow upcoming alarm to be cancelled for just that day
Last modified: 2011-11-06 23:22:49 UTC
It should be possible to cancel an upcoming alarm but still have it go off the next day. This is for when you wake up early. I think this could be done by providing an option in the alarm menu. The use case is that the user is already wide awake, so making them navigate into the alarm menu shouldn't be too bad. People have asked for a shortcut function though, so the feature would ideally be mappable to a button. It should only be necessary to cancel the next alarm, so an item in the top-level alarm menu might do. "Cancel Next Alarm" (a bit long). Not sure where to put it though. A few people on the forums have asked for this and it would certainly fit my usage as well.
This would be great, especially mapped to a button for fast access. Perhaps a press to hold, or confirmation, might be necessary to avoid accidentally pressing the mapped cancel button and not have the morning alarm go off!
Please also fix this for SqueezeNetwork as well. I'd also like the functionality to indefinitely cancel all alarms (for going on vacation, etc). And to be able to re enable them later, of course. I also think this should be a button on the front and would happily give up a favorites button to have this feature!
As I already mentioned in the thread. Can we also have an option to cancel all the of the day's alarms. Handy for public holidays. And be able to assign these new options to the preset soft keys.
For cancelling all the day's alarms or going on holiday, use the All Alarms On/Off feature at the top of the Alarm menu. Then just get into the habit of checking your alarms are set before going to bed (tap the snooze button once/twice, depending on whether the date/time screensaver is displayed). Cancelling just the next alarm is a case that isn't currently addressed as there might be someone else that still needs waking up. All Alarms Off should do the rest. I know this won't please everyone, but we need to keep things simple. Mapping to a button will probably be a power user feature that requires editing the default.map file.
Thanks Max, If the preset buttons are assignable through the default.map and the "Cancel next alarm" is assignable, then I can live with that.
Can I edit default.map when using SqueezeNetwork?
Almost certainly not, I'm afraid. If you can think of a button on the front that could be intuitively used by all users to cancel an alarm and would not detract from the current functionality of the Boom, please suggest it. Or is there another way?
Dean, can you add your comments to this.
I'm worried about feature-creep on this. I'd hate to add another item to the list that would just confuse and not make life that much easier for anybody. That said, what about adding a third state to All Alarms which would rotate between: Alarms All On Alarms All Off Alarms On Tomorrow Again, I think we need to simplify, so unless we can find an elegant solution, I'd rather punt.
If we do this, I think a key feature is the ability to cancel just the next alarm. The scenario is two people sharing an alarm clock, one getting up significantly before the other. The first person wakes up early and wants to cancel their alarm so it doesn't go off, forcing the second person to wake up and stop it. Key is that the second person's alarm still goes off at the appropriate time so they can get to work. 'All Alarms -> On Tomorrow' wouldn't do this. This can be done at the moment, of course - the first person just goes to their alarm and turns it off. However, they then have to remember to turn it on again for the next day. Thinking caps on!
I had the same concern that Dean had about feature creep regarding the initial enhancement request when I read some of the new suggestions. I agree with Max - that goal is to avoid half-awake-stumbling and simplify the disabling of the early alarm. Any other alarm disable feature seems to fall easily enough under the All Alarms Off or Single Alarm Off functional, as user's are presumed awake and cognizant at that time. It would be disappointing (especially to my wife!) if the primary feature request was squashed due to coat-tailed enhancements. Dean - I didn't understand how "Alarms On Tomorrow" addressed this enhancement.
*** Bug 8931 has been marked as a duplicate of this bug. ***
Targeting Enhancement bugs
I can think of a few easy ways to map this 1) When you hold snooze it would cancel (say 10 seconds or so) 2) Hit snooze once to display the next alarm, and either have it scroll to an option or hit it again and it pops up an option to cancel the alarm, then press the wheel to enact it 3) Hold the wheel in to cancel the alarm.
I have a custom IR/Boom.map file with snooze.single = snooze snooze.hold = pause which I find very useful. I found hunting for the pause/power button very difficult for me at 6am in the pitch dark. Knowing I just need to hold the snooze button to kill the alarm is very useful to me. If holding the snooze bar when no alarm is active will disable the next alarm, while keeping my custome behaviour working, I'd be very happy.
My typical situation is that the majority of the time I wake up before my alarm goes off only to have it go off while I'm in the shower, and come back to find it's been yelling at me for the past X minutes. Prior to my squeezeboom, I had an alarm clock with an alarm off/on switch that I would swap before it would go off. (Of course that I would forget to turn it ON before going to bed was a different issue)... I think the best solution for would be simple "Skip Next Alarm" and/or "Skip Today's Alarms" menu items.
I just got my boom, and this is pretty obvious function it should have. I'm also that kind of person that wakes up 10min before the alarm so a simple skip function would make me very happy. And of course if don't set any alarm I either sleep over or wake 2 hours before time :-/ hence me needing an alarm clock anyway ( so that I can wake 10 minutes before i goes of )
removing the target - we should re-consider this for inclusion with 7.5. Baby's alarm UI is much closer to this, and we should mimic it on Boom/Classic too
Weldon to review the alarm layout
I agree with one of the comments here that a hard key press to disable the next alarm should have been mapped in from the beginning, its what all digital alarms do. I think the suggestion of holding the snooze button for 10 or 15 seconds would disable the next set alarm would a good one. the alarm would then rest itself to be re-enabled for its next set time. Additionally something like holding the snooze and pressing the forward arrow would turn all alrams off to cater for extended absence.
Matt Weldon doesn't work for us any more.
Any chance of this bug at least being assigned so that it might get some focus for 7.6 It has been open for 18 months without any progress being made and is probably the most annoying thing about the Boom. I have the Boom beside my bed and don't consider turning off alarms early as a "nice to have" feature. It's core to any alarm clock.
(In reply to comment #20) > I agree with one of the comments here that a hard key press to disable the next > alarm should have been mapped in from the beginning, its what all digital > alarms do. I think the suggestion of holding the snooze button for 10 or 15 > seconds would disable the next set alarm would a good one. the alarm would then > rest itself to be re-enabled for its next set time. > Additionally something like holding the snooze and pressing the forward arrow > would turn all alrams off to cater for extended absence. This is prefered solution for me too! Please, it should be solved ASAP.
Unassigned bugs cannot have a priority.