“Sound” and “command” options should not be mutually exclusive

Bug #1185992 reported by Tina Russell
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Alarm Clock

Bug Description

In the “edit alarms” dialog, you’re given a radio-button choice between whether the alarm should play a sound, using the applet’s own UI, or start a command. You can’t choose both, which is counterintuitive to me; there are many different reasons why you might want to wake up using the applet’s own UI, and have a process start at the same time. (I might want to get a background process started, I might want it to make a log entry, etc.) (You could set two identical alarms to this purpose, but it would be cumbersome and impractical, especially for timer alarms that start counting down the moment you finish editing.)

The easiest UI solution would be, simply, to change the radio buttons to check boxes. Under the hood, this would take a little more work (the underlying GSettings would have to change, for instance, I would imagine), but I hope it wouldn’t be too hard. Thanks!

Johannes H. Jensen (joh)
Changed in alarm-clock:
importance: Undecided → Wishlist
milestone: none → 0.4
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers