| File Variables |
| Argument passing - Subroutines and Functions - Mike Pope |
| RevTech Replies - Mike Pope (RevTech UK Ltd) |
| Symbol Table Structure |
| @ATTACK - @Default.Stops |
| QTIPS - Stop Lists |
| Reader's Clinic - Stop Lists |
| QTIPS - Default Stop Lists |
| QTIPS - Manipulating XREF formulae. |
| Reader's Clinic - Capture Command and Captured Keystrokes |
| Make.Index |
| Capture |
| REVMEDIA Revisted |
| QTIPS - Assorted Oddments |
| Capture Playback and Convert.Keystrokes |
RevMedia FKB
| Document | V3I9A3 |
| Title | QTIPS - Assorted Oddments |
| Keywords | DEBUGGER PDISK CAPTURE |
| Text | Don't forget that in the debugger VARIABLES can be examined one at a time (starting FROM the passed VARIABLES and moving on to the other variables) by typing /# at the ! prompt where # is equal to the number of the variable to look at (Thanks to Jerry McRae Ron Collins et al) PDISK does now work in 2 11 and it is backwards compatible to Rev G At last you can stop USING CAPTURE /CR= Thanks to Matthew Crozier of Vernon SYSTEMS Ltd for reminding us that in the debugger pressing F10 produces an @FM F9 and @VM right down to F1 which produces a char(245) (Volume 3 Issue 9 Page 4) |
Page last modified: 31/01/03