#: 9332 S3/Languages
    29-Jan-91  23:23:14
Sb: #9311-#'C' help
Fm: Jim Peasley 72726,1153
To: Steve Wegert 76703,4255 (X)

Steve;

  Glad to hear that we can do away with the pos_cur(x,y) stuff... now all I
need to do is figure out how to position the input fields in the add_event
function!  Maybe this weekend.

 > However ... I'm now seeing a '1st' in the type of event field, if there's
 > nothing normally there. For instance, a run of dateck brings up Ash 
 > Wednesday. There's nothing special suposed to be in the type of event 
 > field, yet I see a '1st'.
 >  I'm also seeing something wierd with todays date ... the year seems to 
 > be munged.

  The 1st that you're seeing is due to the fact that I changed the logic a bit
to not display a year span for annually recurring events like Christmas, etc.
By setting the year field for such dates to 00, no year span gets printed.
  However... for events such as Ash Wednesday, Easter, Thanksgiving, etc. that
do not fall on the same date each year, it's necessary to manually edit the
dates.file to re-set these dates to the current day/year.
  At some point, I'd like ts incorporate a way to dynamically calculate these
dates, but I don't remember how most of them are calculated.  Labor Day I
know, but not the rest of them!  Anyone???

 >  I'm also seeing something wierd with ttdays date ... the year seems to 
 > be munged.

  What version of the Kreider libs do you have?  I remember a message from
someone saying that the localtime() function was fixed? in the 12/10/90
release - that's what I'm using.

 ...Jim

p.s.  You share the same B'day as our oldest daughter. (19 this year)


There is 1 Reply.