]>
       

Drive Clocky yourself


   Clocky can be driven by other applications. The main Clocky's data
   structure is documented and can be accessed by other programs. You, as
   the programmer, just need to find where the Clocky's data structure is.
   You do it easily - by getting the value of 'JCLK' Cookie.

   You'll get a pointer to data structure shown in JCLKCOOK.H file. After
   checking the name and version data fields (have a look into VYPIS.C, for
   example) you can start changing actual parameters of Clocky.

   The most important is probably the bit field. Every function or feature
   of Clocky has assigned one bit in this 32-bit long variable 'parametry'.

   An example from real application: I also develop the Atari800 software
   emulator of 8-bit computer for Falcon. The emulator installs its own
   keyboard handler (as usually every game or demo does), so Clocky doesn't
   get informations from keyboard neither mouse while the emulator runs and
   that's why the Clocky screensaver is not resetted even if you type
   something in the emulator. The result is clear - after some time Clocky
   disables the screen output to save screen. So what did I do? I simply
   put a small function into the Atari800 emulator that searchs for Clocky
   and if it finds them, it disables the screen saver while emulator is
   running, by simple

   original_saver = parametry.Saveron;
   parametry.Saveron = FALSE;

   Of course that I want to restore the original values when emulator ends.

   parametry.Saveron = original_saver;

   and that's all. This ensures screen saver does not become active when
   you play your favourite game from 1980's. Can you feel the power hidden
   in this driving of Clocky from your applications?