View Single Post
Posts: 277 | Thanked: 319 times | Joined on Jan 2010
#1126
Originally Posted by ajalkane View Post
I could not reproduce this.

I tried:
- alarm in 1 minute
- default sound
- snooze 8 minutes
- used "Run rule's actions"
- disabled from clock application
- changed the time to couple minutes later
- saved

No crash.
I tested some more. If you have the clock app open in the background it's not reproducable. Close it, and it happens every time.

Originally Posted by ajalkane View Post
I'm not sure I understand.

Was a "not" missing in that sentence? Because I just noticed that in the new version, even after pressing "Stop" the alarm is not deleted from clock application. It just becomes inactive. I think in the previous version it was really deleted.

This is not a huge thing for me personally, as activating the alarm again does not create a new entry but instead the old one is reused.

But this definitely requires some testing, as I worry a bit that in some scenarios the alarm might be duplicated (ie. many entries with same title in clock application) which would not be nice.
Again, if you have the clock app open, it seems like it's not deleted when, in fact, it is. This happened in the previous version, too. I think it can't be helped.

Originally Posted by ajalkane View Post
Yes... missing "sound" attribute caused the alarm to be undisablable (not sure that's a word either). It's unfortunate that it doesn't use the default now, but I think this is the lesser of two evils. One can always explicitly define the alarm sound.
I agree, this is much better.

Last edited by slarti; 2013-02-20 at 16:31.
 

The Following User Says Thank You to slarti For This Useful Post: