 |
Fizgar
Magician
Joined: 07 Feb 2002
Posts: 333
Location: Central Virginia
|
 Posted: Sun Oct 23, 2011 6:27 am
[BUG 3.34] Midnight alarms bug
|
Open the untitled session and copy in the following two alarms.
| Code: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger type="Alarm" priority="20" copy="yes">
<pattern>1</pattern>
<value>#show %alarm(test);#show %time</value>
</trigger>
<trigger name="test" type="Alarm" priority="10" copy="yes">
<pattern>00:01:00</pattern>
<value>#print alarm fired</value>
</trigger>
</cmud>
|
Now set your system clock to 11:59pm. Sit back and drink a tasty beverage for two minutes. At the sixty second mark %alarm(test) goes from 60xxx to something like 86457676. |
|
_________________
Windows Vista Home Premium SP2 32-bit
AMD Athlon Dual Core 4400+ 2.31 GHz
3 GB RAM
CMUD 3.34 |
 |
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Sun Oct 23, 2011 2:58 pm
|
not really a bug, I think. The alarm is executing, and thus is no longer counting down. You see much the same thing, I believe, if the alarm is disabled.
|
|
_________________
EDIT: I didn't like my old signature |
|
|
|
Fizgar
Magician
Joined: 07 Feb 2002
Posts: 333
Location: Central Virginia
|
Posted: Sun Oct 23, 2011 4:45 pm
|
The alarm above doesn't fire when I tested though. When %alarm(test) get's to around 60 seconds right before midnight there is 1 minute before it should fire. Once my clock strikes midnight, the timing mechanism of CMUD, %alarm(test) is using resets to 24 hours worth of milliseconds rather than keeping on with the 60 seconds worth it should be tracking. The #print alarm fired is never displayed.
|
|
_________________
Windows Vista Home Premium SP2 32-bit
AMD Athlon Dual Core 4400+ 2.31 GHz
3 GB RAM
CMUD 3.34 |
|
|
|
|
|
|
