Hello Paul!

Tuesday September 24 1996 21:25, Paul Wankadia wrote to Andrew Seeger:

PW> Hi, I think I mailed you before about the ANSI graphics within your
PW> program. This time, it's about that clock thingy :)

Thats cool, i think i have worked out how to work the ansi, when i get some
more time on my hands i willbe able to try it out.

PW> Just save in C format (refer to previous message) and you will have
PW> them hard-coded within the program!

No wazzas!

PW> You don't REALLY need it...

I sortof thought that, although it appears to have some good routines,
although i am at a loss at times as to how to use them :-) There are no docs
that come with it, for beginners like me, this makes life a little more
interesting.

AS>>> 2... A clock routine, to display the clock and continually

PW> Find a spot in your program where it is waiting for user-input or the
PW> like and while it is idling, make a call to the clock routine (or
PW> WHATEVER you want done!) ...  This is a snippet of my code in a
PW> user-input routine :

Yep, figured that out, its mainly for use when the program is doing nothing in
particular and for a keypress etc...

== cut ==

PW> === bit of code ===
PW> // special variables

== cut ==

PW> I hope I've not trimmed any of the essentials out, but I think it's
PW> all in there...  I've used a function pointer, so I can put
PW> Get_Input() in a LIB and just call it from any of my programs...

Ah, you had me wondering why you used a function pointer! Tis clearer now.

FA>> You just call the function from where ever there is a bit of not
FA>> much to do, and it should be fairly smooth. Of course if the
FA>> program gets tied down somewhere for a few seconds the update will
FA>> not happen, but

PW> Just call Get_Input() with like this :

PW>         Get_Input(Input, 81, My_Idler);

PW> where Input is the variable, 81 is the max. length and My_Idler is
PW> your function (N.B. "My_Idler", not "My_Idler()" !!!).

Noted...

Regards,
        Andrew.

--- FMail/386 1.02