Bugs item #853711, was opened at 2003-12-04 00:24
Message generated for change (Comment added) made by kimgrasman
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=432066&aid=853711&group_id=42081

Category: Interface (example)
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Alarm no longer works in 3.1.8.0

Initial Comment:
I tried "alarm 23:58" and "alarm 00:24" - both times I
was told that my timestamp could not be read.

([EMAIL PROTECTED])

----------------------------------------------------------------------

>Comment By: Kim Gr�sman (kimgrasman)
Date: 2003-12-04 08:48

Message:
Logged In: YES 
user_id=551308

Hi,

Something changed in the alarm logic, so it now requires a 
message. We'll probably change this back for the final release 
(unless I'm missing some subtle point on why it works this 
way), but in the meantime you can just put in a bogus 
message, to make it work:

  alarm 23:58 .
  alarm 00:24 zzz

Hope that helps.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=432066&aid=853711&group_id=42081


-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to