In order for this site to work correctly, and for us to improve the site, we need to store a small file (called a cookie) on your computer.
By continuing to use this website, you agree to our cookies and privacy policy.
  
Home page Home page Home page Home page
Pixel
Pixel Header R1 C1 Pixel
Pixel Header R2 C1 Pixel
Pixel Header R3 C1 Pixel
Pixel

Capture

Those readers in possession of the August/September free diskette will have noticed that in running the demonstration program, use was made of a Capture Script and embedded Catalyst calls as mentioned in issue 1 of REVMEDIA. But looking around the disk you may have noticed that there were no capture scripts. So how did it work?

Once again we come back to INPUT.CHAR. If information exists in a system variable called @PLAYBACK, this will be processed in preference to the keyboard buffer. Thus all "replay captured keystrokes" does, is to load @PLAYBACK with the character string to replay. Note that whilst ASCII characters can be entered directly, scan codes must be entered as such, EG @PLAYBACK = CHAR(27) : "Hello there" : CHAR(0) : "C".

To embed catalyst calls within the script to play back, the catalyst code and command must be surrounded by a special "pseudo scan code" of CHAR(0) : CHAR(127). Thus to use a program to run a window from TCL, stop before prompting for the key to display a help message, then auto-enter the key, the code would be


0001            EQU D$    TO CHAR(0) : CHAR(127)
0002            EQU CR$   TO CHAR(13)
0003            @PLAYBACK = "WINDOW DEMO.WINDOW" : CR$
0004            @PLAYBACK := D$ : "HLP Help text" : D$
0005            @PLAYBACK := "DEMO.KEY" : CR$
0006            * Call TCL window
0007            EXECUTE ""

(Volume 1, Issue 6, Page 6)
Pixel
Pixel Footer R1 C1 Pixel
Pixel
Pixel
Pixel