Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!kodak!ispd-newsserver!garden.ssd.kodak.com!weimer
From: weimer@garden.ssd.kodak.com (Gary Weimer (253-7796))
Newsgroups: comp.windows.open-look
Subject: Re: calendar tool weirdness
Keywords: cm, OpenWindows 2
Message-ID: <1991Apr12.163553.1100@ssd.kodak.com>
Date: 12 Apr 91 16:35:53 GMT
References: <1991Apr12.130031.4684@watdragon.waterloo.edu>
Sender: news@ssd.kodak.com
Reply-To: weimer@ssd.kodak.com
Distribution: na
Organization: Eastman Kodak Co.; Rochester, NY
Lines: 35


In article <1991Apr12.130031.4684@watdragon.waterloo.edu>,
phcalama@dial.waterloo.edu (Paul Calamai) writes:
|> I'm experiencing the following weirdness with the calendar
|> tool under OpenWindows2 on a Sparcstation2 running OS4.1.1:
|> (1) If I create an appointment that starts 1hr 15min from
|>     the current time with the mail notification set to 1 hour
|>     in advance, and I stay on the node, I get the mail ~ 1 hour
|>     in advance.
|> (2) Under the same scenario if I log off the node and return to
|>     it some time after the apointment I don't have any mail
|>     in my InBox relating to the (missed) appointment.
|> 
|> Any ideas about what gives?

I would assume that cm does the time check for mailing the same time it
does the check for bells and popups. i.e. has the algorithm:

    if (time to send mail) mail <params>

instead of doing something like:

    insert appointment into calendar
    if (send mail)
       X = appointment time - notify time # notify time = 1hr in your case
       at X mail <params>
    # we can now ignore mail notification

NOTE: at command could not really be used like this, but you get the idea

Since cm does not tell the system to send the mail at some future time,
cm must be running when the time to send mail actually occurs;
otherwise, it doesn't get set.

weimer@ssd.kodak.com ( Gary Weimer )