Comment 4 for bug 1362803
Revision history for this message
| Nekhelesh Ramananthan (nik90) wrote Re: [Bug 1362803] Re: Clock should support creating one-time alarms on any day of the current week | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
On Fri, Aug 29, 2014 at 3:34 PM, Giorgio Venturi <
<email address hidden>> wrote:
> There's at least 2 ways to schedule an alert: Clock and Calendar
>
>
This can get confusing real fast. Imagine a scenario where the current time
is 29th August 18:00 and I set a one-time alarm for 09:00 in the morning.
That alarm would ring obviously ring correctly on 30th August at 09:00 as
expected. However say a few minutes after setting the alarm to 09:00 in the
morning and saving it, I decide that the time is incorrect and I actually
want to instead set the alarm to 29th August (Today) 22:00. How would do I
do that? The moment I had saved the alarm for 09:00, the alarm date was
changed to 30th August. So now when I want to edit the alarm, I cannot go
to the previous date.
Programmatically this is getting way complicated than it should :/
> With the current Clock design, you should indeed be able to set an alarm
> within the next 23h59m
>
> I would leave the option of scheduling an event beyond the 24h to the
> Calendar app
>
>
>