JOURNALING - the quest for the dox goes on

[gudat@avalon.physik.unizh.ch (gudat henrik)]

Journaling - some basic question
 
Now that I know that journaling isn't broken, I'm trying to write a
driver. But since some important information is missing, here are some
questions I have. Please: those who know the answers to the questions,
answer! If I will ever get this done, I'll post the source code so we
can finally enter the age of desktop macros...:)
Maybe we can find out together how we get that done (Jason - are you
listening??:)
 
- One of the possible calls to the journaling driver is GetNextEvent.
However, the event record hasn't a fixed length - it can be the 'old'
record or the extended one. How many bytes have to be preserved?
 
- When playing back a sequence, I put the data into the memory
locations that start at resultPtr. Is that correct?
 
- as I wrote before, this silly GetTick (or what it was..) is executed
dozens of times per second. Which of those calls can be ignored? (I
have noticed that there are about 3 calls that occur constantly,
depending on the situation)
 
- now the most important question: HOW DOES PLAYBACK WORK?
The Event Manager returns JournalFlag=record and resultPtr=pointer to a
data structure - but what about the JournalCode? If this word is
meaningful, what happens when JournalCode does not match the current
packet? Just advance (in the macro sequence) until one of this kind
appears? If JournalCode does not contain anything of interest, how does
the Event Manager know what action comes next?
 
BTW (and this is NOT a joke): my toolbox ref has just fallen into two
pieces - guess on which page...
 
Thanks a lot!!!!!!!!!
 
Henrik

-- 
Bright Software | gudat@avalon.physik.unizh.ch | Oj(/"j2knW(/E.238d7ENs
  P.O. Box 18   |     ezinfo chat: tekkno      | ~'?"K*d|so+wom.mkwAA]
4153  Reinach 2 | gudat@ezinfo.vmsmail.ethz.ch | {shrinked list of all
  Switzerland   |  phone +41 61 261 54 94 CET  |    our programs}