Hi Monty,
I've committed a version with * instead of +, we'll see how that goes.
Thanks for hand-holding ;)
One thing I noticed, though, while testing, was that alarms seem
semi-cumulative. I did this:
alarm 1<enter>
alarm 1 staff meeting<enter>
alarm 1 <enter>
alarm 1staff meeting<enter>
After 1 minute I got 3 alarms (I kinda would've expected 4), all with the
text "staff meeting".
I'm not sure if this is how it was intended to work... Are events to be
queueable or is the last one supposed to override the previous?
I'll leave this for now, and let someone more interested in alarms work
through it...
Cheers,
Kim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Monty Scroggins
> Sent: den 4 december 2003 23:14
> To: [EMAIL PROTECTED]
> Subject: RE: [DQSD-Devel] [ dqsd-Bugs-853711 ] Alarm no
> longer works in 3.1.8.0
>
> I cant imagine it affecting anything... whomever changed it
> probably just
> thought it was cleaner and that the user would never do
> 'alarm 20:00staff
> meeting' and would always have at least one space between the
> time and alarm
> text... or maybe didnt consider that alarm text isnt specifically
> required...
>
>
> Monty
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel
