| Redefining Keys |
| @ATTACK - @Edit.Keys |
| @ATTACK - @Priority.Int |
| @ATTACK - @Macro.Keys |
| @ATTACK - @Macro.Mode |
| QTIPS - Interrupt Proof Error Messages |
| Uncommon Knowledge - WC_Soft_Keys% |
| Background Processing |
| Creating Your Own Background Processes |
| @ATTACK - @Index.Time |
| How Indexes Are Updated |
| Reader's Clinic - Screen Width |
| Screen Grabber |
| Reader's Clinic - Slow Multivalued Screen Display |
| Utility Diskette # 4 |
RevMedia FKB
| Document | V3I8A7 |
| Title | QTIPS - Interrupt Proof Error Messages |
| Keywords | INTERRUPT INPUT.CHAR @PRIORITY.INT ERROR MESSAGE |
| Text | Cameron Christie of McAuley Consultants makes the point that it can be useful to prompt the user for input USING INPUT CHAR without allowing them to access TCL or record macros et al He points out that the simplest way of achieving this is to save off the contents of @PRIORITY INT null @PRIORITY INT then invoke INPUT CHAR When control returns to the calling program restore @PRIORITY INT This technique could be extended to displaying error messages on screen E G Save_PI = @Priority Int @Priority Int = "" Call Msg("Fatal Error" "" "" "") @Priority Int = Save_PI (Volume 3 Issue 8 Page 9) |
Page last modified: 08/02/03