THE DEMONSTRATOR CHAPTER 1 INTRODUCTION The Demonstrator product lets you record mouse movements and keystrokes in a file for playback at a later time. It consists of four separate programs: * DemoRecorder - for recording mouse and keystroke events. * DemoPlayer - for playback of those events. * DemoReport - for translating a recorded event file into a text event file for viewing and/or editing. *DemoCompile - for translating a text event file into the format used by the player. All four programs may be run from either the Workbench using icons or from the CLI. In order to increase awareness of The Demonstrator we are allowing free distribution of a scaled down version of the player program as a demonstration of its capabilities. The FreePlayer program can be freely distributed for non-commercial purposes ONLY! Anyone wishing to distribute our player program with a commercial product may obtain a license from Meridian Software, Ind. A special complete version will be produced with the licensee's name prominently displayed in a window when the DemoPlayer is started. NOTE: The Demonstrator is written to run using AmigaDOS Kickstart Version 1.2. It will not run on previous versions (1.1 or 1.0). You should read the "Getting Started" section first. It will give you enough description of the Demonstrator tools to get you started. Following the "Getting Started" section are individual sections that describe each of the four programs in much greater detail. CHAPTER 2 MATERIAL LIST Included with The Demonstrator are the following: * This Manual. * 1 diskette with the following directories and files: .info - disk icon DemoRecorder.info - DemoRecorder icon DemoRecorder - DemoRecorder task DemoPlayer - DemoPlayer task DemoPlayer.info - DemoPlayer icon DemoEdit - The editing directory DemoEdit.info - DemoEdit directory icon DemoReport - DemoReport task DemoReport.info - DemoReport icon DemoCompile - DemoCompile task DemoCompile.info - DemoCompile icon Most of the files for a WorkBench disk are also included. CHAPTER 3 GETTING STARTED The first thing you should do is fill out the registration card. it is important for you to send this card in to us. We will keep you informed about upgrades and provide hints and tips through our newsletter. MAKING A BACKUP You should make a backup copy of The Demonstrator disk. The Demonstrator has not been copy-protected in order to allow you to install these utilities on hard disks, RAM disks, split between floppy disks, or any combination. Respect our desire to provide you with flexibility by helping us prevent illegal copyright infringement! You can also copy the various The Demonstrator files, as listed in Chapter 2, as a form of backing up the software. YOUR FIRST SESSION If your AMIGA has not been turned on, or does not have Kickstart V1.2 installed: power up, and install Kickstart V1.2. Otherwise, reboot your Amiga by holding down the CTRL key and pressing the two Amiga keys on either side of the space bar. Place your backup copy of The Demonstrator in the default drive when prompted for the Workbench disk. Wait until the familiar Workbench icon(s) are presented to you. Double-click on The Demonstrator disk icon. A large window should appear with the DemoRecorder, DemoPlayer, and several other icons. Double-click on the example tape icon labeled: Example. A copyright message window will appear. Please read this message at least once. You can make this window disappear quickly by hitting any key on the keyboard or the left mouse button. A window appears asking you to Hit Left-Amiga F1 to start (NOTE: Left-Amiga is the key immediately to the left of the Space Bar, on some Amiga models this key has the Commodore symbol). Press and hold the Left-Amiga and then press the F1 key. The DemoPlayer status window provides statistical information throughout the playback of the tape file. This window will go away if the mouse gets near it during the playback. This example will show you the information stored in the player's icon. Remember, during playback the mouse and keyboard is locked out except for certain special DemoPlayer keys. This example will next open the DemoEdit drawer in order to show you where the DemoCompile and DemoReport files reside. These two programs provide you with the ultimate control for your demonstrations or tutorials created by The Demonstrator. When the DemoPlayer is finished playing the tape file, a brief message will appear saying: DemoPlayer exiting. This means the program is no longer running. YOUR FIRST AMIGA RECORDING SESSION Let's try a simple recording session. First, double click on the DemoRecorder icon. A window will appear asking you to enter the name of the playback file. Enter Ram:Temp1 followed by RETURN. Hit the Left-Amiga F1 to begin recording: First double click on the System drawer icon and wait for all of the new icons to appear. Double click on the CLI icon. A CLI window will open with a 1> prompt. Type in from the keyboard: "; Thanks for buying The Demonstrator!" Wait for two secons (or more), the press CTRL-X. The line you typed will disappear. Type: ENDCLI followed by the RETURN key. The CLI window should go away. Click on the close window gadget for the System window (the window with the CLI icon). The window should go away. Hold down the right mouse button and move the mouse in a circle (this movement will be recorded), then release the mouse button. Hit the Left-Amiga F7. This will make the playback automatically replay itself, then it will save the recorded session, and exit the DemoRecorder program. PLAYING YOUR FIRST RECORDING Double click on the DemoPlayer icon. A window will appear asking for a filename. Enter RAM:Temp1 (from the last section) followed by the RETURN key. Hit the Space Bar to skip reading the copyright message. Press the Left-Amiga F1 keys to start the playback. you will now see the session you recorded in the last section perform itself. It will continue to perform the playback until you hit the exit button. Before hitting exit, you may want to try these options: Left-Amiga F4 - Speed up playback. Left-Amiga F5 - Slow down playback. Left-Amiga F6 - Toggle Status window. Use Left-Amiga F3 to exit the program. CHAPTER 4 RECORDING EVENTS WITH DEMORECORDER DemoRecorder records all keystrokes and mouse movements and stores those events in the file that you specify. You can control DemoRecorder using the first seven function keys. To activate any of the function keys, you hold down the LEFT Amiga key (the key to the left of the space bar) and the function key at the same time. The function keys have the following meaning (the LA- means to hold down the LEFT AMIGA key at the same time as the following function key): LA-F1 - Start/Resume - Start or resume recording events into the file. You must hit this key when you first start DemoRecorder in order to start recording. LA-F2 - Pause - Pause recording. Hit this key to stop recording events without causing DemoRecorder to exit. To resume recording you must hit LA-F1, the Start/Resume key. LA-F3 - Exit DemoRecorder. Hit this key to stop recording and exit DemoRecorder. The record file will be closed. After exiting, you can use DemoPlayer to play back the recorded events, or use DemoReport and DemoCompile to make changes to the record file. LA-F4 - Terse Mode On (default). When DemoRecorder is first started, terse mode is ON. This means that DemoRecorder will not record mouse movements if the mouse buttons are not depressed. It will record mouse clicks and mouse movements made with when either menu button is depressed. Terse mode exists so that record files can be smaller. LA-F5 - Verbose Mode On. This mode is the converse of terse mode. When in verbose mode, DemoRecorder will record ALL mouse and keyboard events. Note that when in this mode, the record file will get large very quickly. LA-F6 - Toggle status window. Hit this key to make the status window appear or disappear. Note that if the mouse sprite gets too close to the status window, it will automatically disappear. if the status window has disappeared, hitting the LA-F6 key will make the window reappear. LA-F7 - Looping, save, and exit. If you hit this key, and endless loop is inserted into the current recording event file. The file will be saved, and you will exit the DemoRecorder. During playback the fill will automatically loop to the beginning. It is very important that you return the system to the same envirionment used when the recording session was begun or the looping may not work properly. DEMORECORDER STARTUP OPTIONS DemoRecorder has three startup options: 1) DISPLAY_STATUS - Display_Status is a flag that specifies whether the DemoRecorder status window will be displayed. If Display_Status is set TRUE, the status window can be displayed; if set FALSE, the status window will nto be displayed. 2) UPDATE_FREQUENCY - Update_Frequence specifies the number of events that occur between updates of the status window. note that any input event (including timer events) are counted to determine when the update will occur. This means that the status window will update even without moving the mouse. For example, if XXX were 50, the window would update at least once every 5 seconds since there are 10 timer events per second. 3) MESSAGE_SCREEN - Message_Screen is a flag that specified whether the DemoRecorder's message window will attempt to appear in the frontmost screen. This could be undesireable when editing a drawing since the window may interfere with the drawing. If Message_Screen is set to TRUE, the message window will always appear in the Workbench screen (the Workbench screen will automatically come to the front briefly); if set FALSE, the message window will attempt to appear in the current frontmost screen. The default values for the startup options are: DISPLAY_STATUS=1| UPDATE_FREQUENCE=50| MESSAGE_SCREEN=0| NOTE: The bar '|' is used to separate the tools. ACTIVATING DEMORECORDER FROM THE WORKBENCH There is a separate icon for DemoRecorder (the DemoRecorder.info file). To activate DemoRecorder, you double click on the DemoRecorder icon. DemoRecorder will start by putting up a window asking for the name of the file into which events are to be recorded. Any valid Amiga file name is allowed. If the file already exists, DemoRecorder will open a window to ask you if you want to overwrite the file that's already there. After you have entered the file name, continue by selecting the OK gadget or hit RETURN. If you wish to cancel the recording session, select the CANCEL gadget, and DemoRecorder will exit. After entering the filename, DemoRecorder is ready to begin recording. It will start recording events after you hit the LEFT-AMIGA-F1 key combination. When run from the Workbench, DemoRecorder will create an icon for the file that you record to. After recording is finished, you can click on this icon to activate the DemoPlayer to play back the file you just recorded. NOTE: You may have to change the icon's default tool to reflect the location of the DemoPlayer (found in the "info" section described below). You can display or change the startup options for the DemoRecorder tool by clicking once on the DemoRecorder icon and selecting the "info" item from the Workbench menu. This will activate the info tool which can then be used to modify the values of DISPLAY_STATUS, UPDATE_FREQUENCY, or MESSAGE_SCREEN. To change Display_Status, Update_Frequence, or Message_Screen first select the 'Tool Types' gadget. Next, use the arrow gadgets to scroll the contents displayed in the string gadget until the value you wish to modify is displayed. To change this value, select the string gadget, and enter the value that you wanted to change. Once your change is correct, make sure the vertical bar key '|' is the last character, then press the RETURN key. The RETURN key MUST be pressed to save the change. Finally, select the SAVE gadget with the mouse to save all changes to the icon file. For example, to make DemoRecorder update the status window every 20 events, change the entry to read: "UPDATE_FREQUENCE=20|". ACTIVATING DEMOCRECORDER FROM THE CLI DemoRecorder can be run from the CLI. The command line looks like: RUN DEMORECORDER filename [-d] [-uXXX] [-m] where "filename" is the name of the file you wish to record to. The optional argument in brackets set the following flags: -d This switch sets DISPLAY_STATUS to TRUE. Note that the default value for DISPLAY_STATUS is FALSE when run from the CLI. -uXXX This switch sets the update frequence. XXX is the number of events that occur between updates of the status window. -m This switch sets MESSAGE_SCREEN to TRUE. Default is FALSE from CLI. When DemoRecorder is started from the CLI, it displays an introductory message. It then checks to see if the file that you are recording already exists. If the file already exists, DemoRecorder will open a window to ask you is you want to overwrite the file that's already there. If you click on the YES gadget, or are recording to a new file, DemoRecorder is ready to begin recording. If you click on the NO gadget, DemoRecorder will exit. To begin recording, you must hit the Left-Amiga F1 key combination. Note that when run from the CLI, DemoRecorder does not create an icon for the file you are creating. Note also that when run from the CLI, you should use the RUN command to activate DemoRecorder. DEMORECORDER STATUS WINDOW When DemoRecorder is running, if the status window in enabled (DISPLAY_STATUS is TRUE) you can toggle the appearance/disappearance of the status window. The DemoRecorder status window contains the following information: 1. x and y coordinates 2. Record/Pause 3. Terse/Verbose 4. Elapsed time 5. Byte count * - The x and y coordinates are Intuition coordinates. This means they are with respect to the upper left hand corner of the screen and independent of what windows are present on the screen being displayed. * - Record/Pause shows whether DemoRecorder is recording events; if in Record, events are being recorded; if in Pause, events are not being recorded. * - Terse/Verbose shows whether DemoRecorder is in Terse mode or Verbose mode. Recall that in Terse mode, DemoRecorder will only record mouse button events, mouse move events made when either mouse button is held down, and raw key events. In Verbose mode, it records all mouse and key events. * - Elapsed time shows the total time that DemoRecorder has been in record mode during this recording session. Elapsed time begins with the first event recorded after entering record mode. Elapsed time does not increment when DemoRecorder is paused. * - Byte Count shows the current size of the record file in bytes. The status window updates at a minimun of every UPDATE_FREQUENCE events. It will update more frequently if one of the mode flags changes. For example, the window will update immediately if you put DemoRecorder into Pause mode from Record mode. CHAPTER 5 PLAYING EVENTS WITH DEMOPLAYER DemoPlayer "plays" back events that have been previously recorded. It completely duplicates the events that were recorded including the timing of the keystrokes and timing of the mouse movements. While events are being played back. DemoPlayer locks out normal keyboard and mouse input. To control the playback, you use the LEFT Amiga key with the first six function keys. The function keys have the following meaning: LA-F1 - START/RESUME - Resume (or start) playing back events. If the AUTO_START flag is FALSE (the default), then you must hit the Start/Resume key before DemoPlayer will begin to play the events in the file. The Start/Resume key is also used to Resume playing events after the Pause key is hit. LA-F2 - PAUSE - Pause playback. Use this key to pause the playback of events. If the PAUSE_ENABLE flag is set to TRUE, DemoPlayer will release control of the keyboard and mouse during the pause. If PAUSE_ENABLE is set FALSE, DemoPlayer will continue to lock out the keyboard and mouse. LA-F3 - EXIT DEMOPLAYER. Hit this key to stop event playback and exit DemoPlayer. This key lets you exit DemoPlayer before it has finished playing all the events in the file. LA-F4 - SPEED UP PLAYBACK. Hit this key during playback to increase the speed with which events are played. When DemoPlayer starts, the default playback speed is the same speed set by the SPEED option and defaults to the speed at which events were recorded. Hitting the Speed Up key decreases the delay between events causing them to be played faster. Each hit of the Speed Up key will cause a 5% increase in playback speed. Repeated hits of the Speed Up key will continue to speed up playback until playback becomes limited by processor speed. LA-F5 - SLOW DOWN PLAYBACK. Hit this key to slow down playback speed. For each hit, the playback speed will decrease by 5%. There is no limit to the slowness of events except that events must occur more often than one per hour. LA-F6 - TOGGLE STATUS WINDOW. Hit this key to make the status window appear or disappear. DEMOPLAYER STARTUP OPTIONS In addition to the function keys which may be used during playback, DemoPlayer also recognizes several options that may be selected when DemoPlayer is first started. (How to set these options is discussed separately in the sections below.) These options are: * - SPEED - DemoPlayer allows you to adjust the starting playback speed. The default speed will play back at the same speed as events were recorded. This speed is represented by the number 100. To make events play faster you set speed to a lower number. For example, to make events play approximately twice as fast as they were recorded, set the speed to 50. To make events play back at one half the speed that they were recorded, set the speed to 200. * - PAUSE_ENABLE - Pause_Enable allows you to tell DemoPlayer whether the mouse and keyboard should be locked out during a pause. If you want to be able to move the mouse and enter keystrokes after you hit the PAUSE key, then PAUSE_ENABLE should be set TRUE. The default is for PAUSE_ENABLE to be set FALSE. * - AUTO_START - Auto_Start allows you to tell DemoPlayer whether to begin playing events as soon as DemoPlayer starts, or to wait for you to hit the RESUME key. If you want DemoPlayer to start automatically, the AUTO_START should be set TRUE. The default is for AUTO_START to be set FALSE. When AUTO_START is FALSE, it gives you the chance to do whatever may need to be done to get things ready for playback. * - LOCK_OUT - Lock_Out allows you to completely lock out keyboard control. When LOCK_OUT is set, DemoPlayer will ignore ALL keyboard and mouse events, including the function key commands that it normally listens to. If you want to lockout all keyboard input, set LOCK_OUT to TRUE. The default is for LOCK_OUT to be TALSE. Note that when LOCK_OUT is set TRUE, AUTO_START will automatically be set TRUE as well. When LOCK_OUT is TRUE, DemoPlayer will only exit at the end of the play file. This means LOCK_OUT should only be used when you are sure that you do not want to exit the play file prematurely. (Of course, you can always exit prematurely by re-booting the Amiga). * - DISPLAY_STATUS - Set Display_Status to TRUE if you want to be able to display the DemoPlayer status window; FALSE to disable the status window. * - UPDATE_FREQUENCE - Update_Frequence specifies the number of events between status updates. The default value is 50. This means that if the status window is displayed, its contents will update every 50 events. Make this a smaller window (as small as 1) to increase the frequence of status updates. For example, if Update_Frequence were equal to 5, the status window would update every 5th event. You should be cautious about making updates too frequent; playback files which have critical timing might not work properly because frequent updating of the status window will make the CPU loading during playback different from CPU loading during record. * - MESSAGE_SCREEN - Message_Screen is a flag that specifies whether the DemoRecorder's message window will attempt to appear in the frontmost screen. This could be undesireable when editing a drawing since the window may interfere with the drawing. If MESSAGE_SCREEN is set to TRUE, the message window will always appear in the WorkBench screen (the Workbench screen will automatically come to the front briefly); if set FALSE, the message window will attempt to appear in the current frontmost screen. * - WINDOW=CON:0/0/1/1/ - This is a tool which guarantees the special event commands will work properly when the player is run from an icon. ACTIVATING DEMOPLAYER FROM THE WORKBENCH To activate DemoPlayer from the Workbench, open The Demonstator window and click twice on the DemoPlayer icon. DemoPlayer will begin by putting up a window to ask you for the name of the file that you wish to play. Enter the name of the file to be played, and select the OK gadget or hit RETURN. If you wish to exit without entering a filename, select the CANCEL gadget. Once the filename has been entered, DemoPlayer will proceed, using the option settings that it finds in the DemoPlayer.info file. For example, if the AUTO_START flag is set TRUE (a 1 in the .info file), DemoPlayer will start playing without waiting for you to hit the RESUME key. Alternately, DemoPlayer can be activated by double clicking on the project icon that DemoRecorder makes when it is run from the Workbench. When activated from an icon, DemoPlayer will use the options found in the .info file, instead of the options found in the DemoPlayer.info file. You can display and/or change the startup options for either the DemoPlayer tool, or DemoPlayer projects by clicking once on the DemoPlayer or project icon, and then, using the right mouse button, select the .info item from the Workbench menu. This will activate the info tool which can be used to examine and modify the default values found in the DemoPlayer.info or project.info file. To change any of the defaults, select the "Tool Types" gadget and modify the value associated with the appropriate name. For example, to change the SPEED to 50, use the arrows to find the SPEED string. Then select the SPEED string, then change it to read "SPEED=50|". After you are satisfied with your change, press the RETURN, and select the SAVE gadget with the mouse. NOTE: You should put the bar'|' at the end of each tool to guarantee separation. For options which are TRUE or FALSE, TRUE is represented by '1', and FALSE is represented by '0'. The default values for the startup options are: SPEED=100 PAUSE_ENABLE=0 AUTO_START=0 LOCK_OUT=0 DISPLAY_STATUS=1 UPDATE_FREQUENCE=50 MESSAGE_SCREEN=0 WINDOW=CON:0/0/1/1 NOTE: The WINDOW=CON: item should always exist & should only be in the DemoPlayer icon. It enables the special command functions to operate properly. ACTIVATING DEMOPLAYER FROM THE CLI DemoPlayer can be run from the CLI. The command line looks like: RUN DEMOPLAYER FILENAME [-a][-l][-p][-sXXX][-uYYY][-m] where "filename" is the name of the file you wish to play. The optional arguments in brackets set the following flags. -a This switch sets the AUTO_START flag TRUE. -d This switch sets the DISPLAY_STATUS flag TRUE. Note that when run from the CLI, the default value for DISPLAY_STATUS is FALSE; this is different from the default value when run from the WorkBench. -l This switch sets the LOCK_OUT flag TRUE. -p This switch sets the PAUSE_ENABLE flag TRUE. -sXXX This switch sets the beginning playback speed. XXX is the number that will replace 100 as the beginning playback speed. -uYYY This switch sets the update frequency for the status window. YYY is the number of events that occur between updates of the status window. -m This switch sets MESSAGE_SCREEN to TRUE. Default is FALSE from the CLI. Note the default for all of the TRUE/FALSE flags is FALSE. For example, to specify AUTO_START, and PAUSE_ENABLE with an initial play rate of twice the record speed you would use the command line: RUN DEMOPLAYER FILENAME -a -p -s50 When running DemoPlayer from the CLI, DemoPlayer does not consult the .info file that may be associated with the file that is being played; it obtains all its option information from the CLI command line. Note also that you should be careful to run DemoPlayer from the same CLI window that DemoRecorder was run from. DEMOPLAYER STATUS WINDOW When DemoPlayer is running, the status window can be made to appear or disappear. The DemoPlayer status window contains the following information: 1. x and y coordinates 2. Rate 3. Time 4. Run/Pause 5. File Position Proportional Gadget * - The x and y coordinates are the current Intuition coordinates of the mouse. * - The Time displayed in the calculated elapsed time into the playfile. This time is not wall clock time; it's just the sum of all the delays contained in the playfile events up to the current event. If the playback speed is the normal value of 100, time should be close to the actual elapsed time. For example, if you change the playback speed to 50, the time value displayed in the status window will be the same when DemoPlayer gets to event 30 as it would be at event 30 for a playback speed of 100. * - Run/Pause shows whether DemoPlayer is currently in Run mode or if it is Paused. * - The file position gadget shows the current file position. As DemoPlayer moves through the playfile, the slide bar moves from left to right. Note that when DemoPlayer is in Pause mode, you can select this gadget and slide it around. This will have NO effect. CHAPTER 6 EDITING EVENTS WITH DEMOREPORT AND DEMOCOMPILE After recording a series of mouse and keyboard events, you can use DemoReport and DemoCompile to make changes to the event file. DemoReport translates the raw data file produced by DemoRecorder into an ASCII file (a file that YOU can read and understand). You can then use any text editor to make changes to the text file. Once you are happy with the changes you've made, you translate the text file back into an ASCII file that can be ready by DemoPlayer by using DemoCompile. ACTIVATING DEMOREPORT FROM THE WORKBENCH To activate DemoReport from the Workbench, open the DemoEDIT drawer and click twice on the DemoReport icon. DemoReport will begin by putting up a window that asks you to enter the name of the file to report. Enter the name of the file and select the OK gadget or hit RETURN. If you don't want to report a file, select the CANCEL gadget. After selecting the OK gadget, DemoReport will put up a status window that shows the event number that it is currently translating. When it is finished, it ups up an exit message and then exits. When run from the Workbench, DemoReport constructs the name of the report file by appending ".rpt" to the name of the file that you enter. For example, if you enter a file name of "test", DemoReport will create (or overwrite) the file "test.rpt". ACTIVATING DEMOREPORT FROM THE CLI DemoReport can be run from the CLI. The command line looks like: DEMOREPORT INFILENAME OUTFILENAME where "infilename" is the name of the event file and "outfilename" is the name of the report file to be created. Note that when run from the CLI, you can use whatever file names you want. Be careful though if you want to use your report file later from the Workbench; the outfilename shoul have the ".rpt" extension. ACTIVATING DEMOCOMPILE FROM THE WORKBENCH To start DemoCompile from the Workbench, open the DemoEDIT drawer, then double click on the DemoCompile icon. DemoCompikle will begin by putting up a window that asks you to enter the name of the file to compile. Enter the name of the file and select the OK gadget or hit RETURN. If you don't want to compile a file, select the CANCEL gadget. After selecting the OK gadget, DemoCompile will put up a status window that shows the line that it is currently compiling. When it is finished, it puts up an exit message and then exits. When run from the Workbench, DemoCompile constructs the name of the input file by appending ".rpt" to the name of the file that you enter. For example, if you enter a file name of "test", DemoCompile will read the file "test.rpt", and create (or overwrite) the file "test". ACTIVATING DEMOCOMPILE FROM THE CLI DemoCompile can be run from the CLI. The command line looks like: DEMOCOMPILE INFILENAME OUTFILENAME where "infilename" is the name of the ASCII event rile and "outfilename" is the name of the event file to be created. Note that when run from the CLI, you can use whatever file names you want. Be careful though if you want to use your report file later from the Workbench; the infilename should have the ".rpt" extension. REPORT FILE SYNTAX When DemoReport is run it creates a text file that can be edited using any text editor. This section describes the format of each type of event that can be described by a single line in a report file. This format is necessarily terse so that report files won't become too large. There are three types of events that can appear in a report file: Raw Mouse Events, Position mouse Events, and Raw Key Events. Comments may be inserted into the report file by placing a semi-colon as the first character on the line. In addition to events, there are several sepecial event commands that are provided for further control to the event file. RAW MOUSE EVENTS Here is an example of a Raw Mouse Event: M LEFT|DOWN secs: 0 usec: 16668 x: 0 Here is a description of the meaning of the fields in the line: M - first field. For Raw Mouse events this MUST be a capital M. LEFT|DOWN - second field. This specifies the type of mouse event. There are several possibilities. The first word may be: LEFT, RIGHT, or MOVE. If LEFT or RIGHT is the first word, it MUST be followed by either UP or DOWN. These type of events are mouse button events. LEFT|DOWN means that the left mouse button is pushed down. LEFT|UP means the left mouse button is released. If the first word is MOVE, it means that the mouse moved; and no buttons were clicked. secs: - third field. This is a descriptive string referring to the following value (seconds). Note that the compiler does not interpret this string, but that there must be a string of some kind in the third field. 0 - fourth field. This number represents the number of seconds between this event and the next event. It can be no longer than 3600. usec: - fifth field. This is a descriptive string just like secs: above. The same comments apply. 16668 - sixth field. This number represents the number of microseconds between this event and the next event. It can be no longer than 1000000 (1 million microseconds = 1 second). x: - seventh field. This is a descriptive string referring to the following value. 0 - eighth field. This is the relative movement of the mouse along the horizontal axis in pixels. For example, if it were a 10, it would mean to move the mouse 10 pixels to the right; a -10 would move the mouse 10 pixels to the left. y: - ninth field. This is a descriptive string referring to the following value. 0 - tenth field. This is the relative movement of the mouse along the vertical axis in pixels. For example, if it were a 10, it would mean to move the mouse 10 pixels closer to the bottom of the screen; a -10 would move the mouse 10 pixels closer to the top of the screen. Here are a few more examples of valid Mouse events: ; ; This is a comment line. Notice that there is a ";" as he first ; character ; M LEFT|DOWN secs: 0 usec: 100003 x: 0 y: 0 M LEFT|UP secs: 0 usec: 66670 x: 0 y: 0 M MOVE secs: 0 usec: 500003 x: 1 y: 1 M RIGHT|DOWN secs: 0 usec: 83336 x: 0 y: 0 M RIGHT|UP secs: 0 usec: 26676 x: 0 y: 0 RAW KEY EVENTS Here is an example of a Raw Key Event: