[EMAIL PROTECTED] writes: <> >> However, when that was drafted (at least the copy I have), the job >> event byte (sending events to jobs) didn't exist yet, I presume it is >> NOT zero'd on exit, but am not sure. > Well my experiments, granted very simple, show the LSB ony is non-zero > the remainder are zero. Mind you, how exactly do I send an event to a job? > > If I PICK the job, or button frame it, then DO it's button, I get the same > event both times - $2D with a Key Stroke of $08.
These are a different kind of event. You need to use a trap (sms.sevt)to send a job event. Used for jobs communication. Eg job A, a game say, is at the top of its program loop waiting for either user input or a job event (using mcallt in EP). Another job, job B, running an independent timer asynchronously, sends a pre-arranged event to job A signifying "Time's up!". This triggers job A's call and drops into the program's time-out handling code. The above it what I do in D-Miner. The Timer toolkit (source code included on www.witteware.com/knoware toolkits/Timer) demonstrates a use of job events. Per _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
