Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 3 days, 3 hrs ago - more...
 |
jellyroll |
2014-04-22
, 00:39
|
|
Posts: 435 |
Thanked: 684 times |
Joined on Apr 2012
@ Netherlands 020
|
#351
|
Originally Posted by freemangordon
Thank you...
|
|
2014-04-22
, 16:59
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#352
|
Originally Posted by Android_808
I have clock-ui 0.6-1+0cssu4+thumb0 installed and given that FMG later posted about a new 0.6-1+0cssu5 in cssu devel, I assume you found the issue with the same version as mine.
Set alarm to 5:00 for example.
Wait till alarm goes off and hit snooze. Alarm time now says 5:10
Disable/uncheck alarm before snooze alarm goes off.
Alarm is now stored as 5:10.
I do not see the problem. For me the alarm sounds, I hit snooze and if I then go to untick the box before the next ring, the original alarm time is showing and stays that way after un-setting.
Using replacement mce...
| The Following 4 Users Say Thank You to handaxe For This Useful Post: | ||
|
|
2014-04-22
, 19:35
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#353
|
clock-ui 0.6-1+0cssu4+thumb0
stock mce.
I've attached screenshots of the process. It seems clicking to deactivate is causing it to see the 'snooze' time as the actual alarm time and then setting it on save. Edit: had to split into 2 to fit upload restrictions.
stock mce.
I've attached screenshots of the process. It seems clicking to deactivate is causing it to see the 'snooze' time as the actual alarm time and then setting it on save. Edit: had to split into 2 to fit upload restrictions.
|
|
2014-04-22
, 19:56
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#354
|
As far as I can judge it, it now acts like this:
The snooze time is displayed when it is linked to a specific date
The initial time is displayed again when it is not linked to a specfic date
To prevent a possible time shift as Android_808 encountered, it would be better to keep displaying the initial time.
At least it should be consistent and not be the cause of a potential time shift.
Never noticed this... I'll try to fix it.. this time.
Last edited by ade; 2014-04-22 at 20:38.
The snooze time is displayed when it is linked to a specific date
The initial time is displayed again when it is not linked to a specfic date
To prevent a possible time shift as Android_808 encountered, it would be better to keep displaying the initial time.
At least it should be consistent and not be the cause of a potential time shift.
Never noticed this... I'll try to fix it.. this time.
Last edited by ade; 2014-04-22 at 20:38.
| The Following 6 Users Say Thank You to ade For This Useful Post: | ||
|
|
2014-04-23
, 20:11
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#355
|
Some additional info on the changes before I am going to upload it:
Alarm with date will now show the original alarm time in the list when snoozing (just like the alarm without date). The main page shows the next alarmtime including snooze (as usual).
About disabling/enabling an alarm time connected to a date:
Technically it deletes/creates a new alarm whenever you toggle it. But when you disable an alarm with date during snooze, it cannot be recreated, as alarmd does not accept the original timestamp (already in the past). As the time shifted to snooze time in the old situation, it could recreate the alarm (using the trigger time in the future).
But.... it does not make sense to disable an alarm that already has a timestamp from the past. This alarm is functionally already disabled, but only the snooze keeps it alive.
So in the new situation, this alarm status will stay enabled as long as snooze is used, but you can no longer "disable" it. This way, the alarm will end up as disabled with the original time plus date as soon as the snoozing ends.
Hope it makes some sense to others
I suspect Freemangordon will push another update to cssu-devel afterwards.
Alarm with date will now show the original alarm time in the list when snoozing (just like the alarm without date). The main page shows the next alarmtime including snooze (as usual).
About disabling/enabling an alarm time connected to a date:
Technically it deletes/creates a new alarm whenever you toggle it. But when you disable an alarm with date during snooze, it cannot be recreated, as alarmd does not accept the original timestamp (already in the past). As the time shifted to snooze time in the old situation, it could recreate the alarm (using the trigger time in the future).
But.... it does not make sense to disable an alarm that already has a timestamp from the past. This alarm is functionally already disabled, but only the snooze keeps it alive.
So in the new situation, this alarm status will stay enabled as long as snooze is used, but you can no longer "disable" it. This way, the alarm will end up as disabled with the original time plus date as soon as the snoozing ends.
Hope it makes some sense to others
I suspect Freemangordon will push another update to cssu-devel afterwards.
| The Following 6 Users Say Thank You to ade For This Useful Post: | ||
|
|
2014-04-23
, 20:54
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#356
|
Alarm with date will now show the original alarm time in the list when snoozing (just like the alarm without date). The main page shows the next alarmtime including snooze (as usual).
About disabling/enabling an alarm time connected to a date:
Technically it deletes/creates a new alarm whenever you toggle it. But when you disable an alarm with date during snooze, it cannot be recreated, as alarmd does not accept the original timestamp (already in the past). As the time shifted to snooze time in the old situation, it could recreate the alarm (using the trigger time in the future).
But.... it does not make sense to disable an alarm that already has a timestamp from the past. This alarm is functionally already disabled, but only the snooze keeps it alive.
So in the new situation, this alarm status will stay enabled as long as snooze is used, but you can no longer "disable" it. This way, the alarm will end up as disabled with the original time plus date as soon as the snoozing ends.
If I click snooze by mistake, can I stop it without having to wait 10 mins to click the stop button.
|
|
2014-04-23
, 21:02
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#357
|
Originally Posted by Android_808
I realized this. But as I said it is not possible to change an alarm in the past. So it will only effect alarms with a date. If you pressed snooze by mistake and want to keep your former alarm as a souvenir, wait for the snooze. If not, simple remove the alarm at that moment.
This I don't
| The Following 2 Users Say Thank You to ade For This Useful Post: | ||
|
|
2014-04-23
, 22:37
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#358
|
Its not about keeping them as souvenirs, its more of an issue of trying to disturb everyone else in the house as little as possible when going to work in the early hours. Deleting isn't really a workable option IMO as it opens the door to people removing to avoid it going off and then forgetting to re-add it.
If you leave the disable code as it was and pass the correct/original time into the edit dialog along with the date of the next recurrence, would that retain the feature of disabling snooze. Disabling alarm would then also save a set of valid params.
Technically it deletes/creates a new alarm whenever you toggle it. But when you disable an alarm with date during snooze, it cannot be recreated, as alarmd does not accept the original timestamp (already in the past).
| The Following User Says Thank You to Android_808 For This Useful Post: | ||
|
|
2014-04-23
, 23:04
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#359
|
Originally Posted by Android_808
Are we talking about the same type of alarms?
Its not about keeping them as souvenirs, its more of an issue of trying to disturb everyone else in the house as little as possible when going to work in the early hours. Deleting isn't really a workable option IMO as it opens the door to people removing to avoid it going off and then forgetting to re-add it.
I am referring to alarms that have gotten a specific date.
This option is not widely used is my experience. If you do not touch the date settings, you will get the alams which act like the ones in the stock clock. This is what you would use to create your weekly wake-up schedule.
I only use alarms with a date set if I know I have to do something in for example 25 days. As it is not in a repeat schedule, I usually delete if afterwards.
If you leave the disable code as it was and pass the correct/original time into the edit dialog along with the date of the next recurrence, would that retain the feature of disabling snooze. Disabling alarm would then also save a set of valid params.
My feeling is that you actually want to set alarms without a date.
| The Following 2 Users Say Thank You to ade For This Useful Post: | ||
|
|
2014-04-24
, 00:58
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#360
|
Originally Posted by ade
The issue lies with alarms set using the repeat function and not those set by date, where your reasoning is valid. Set an alarm for a time and a repeat by days of the week and the set time wanders onwards with each snooze invocation and stays there if the alarm gets "unticked". If it is stopped at the snooze interval ring, then it reverts to the original set time (as it should).
Are we talking about the same type of alarms?
So, the issue actually is one of how to interrupt a snooze cycle without unticking the alarm.
Or should one simply let it ring (until "stop" if one is around, or until a timeout)? Does the latter stop the snooze alarm ringing again? If it does, I assume the original time is kept.
 |
| Tags |
| easter egg, lockslider |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 16:05.