| VERBatim - V16 |
| @ATTACK - @Int.Const |
| @ATTACK - @Move.Keys |
| @ATTACK - @Priority.Int |
| @ATTACK - @Macro.Mode |
| Uncommon Knowledge - WC_Unkeys% |
| Utility Diskette # 3 - Part I |
| Utility Diskette # 4 |
| QTIPS - Positioning Cursors in AMV fields |
| Uncommon Knowledge - WC_WI_NEXT% |
| Uncommon Knowledge - WC_WI_NEXT% (Continued) |
| Redisplaying Multi-Values |
| Uncommon Knowledge - WC_Amv_Action% |
| QTIPS - Positioning Cursors in AMV fields |
| QTIPS - Using AMV.ACTION To Save Coding Time |
RevMedia FKB
| Document | V3I5A5 |
| Title | QTIPS - Positioning Cursors in AMV fields |
| Keywords | WINDOW_COMMON% WC_AMV_ACTION% WC_WI_NEXT% WC_MV_NEXT% |
| Text | Mike Nourse of MN2 generously points out that it can sometimes be desirable to position the input CURSOR on a specific row/prompt intersection in an AMV after altering the contents of the AMV Unfortunately setting WC_AMV_ACTION% to 4 (to redisplay the contents) always sets WC_MV_NEXT% back to 1 resulting in the CURSOR returning to line 1 of the AMV Mike points out that putting an "@" in front of WC_MV_NEXT% instructs the window processor to leave WC_MV_NEXT% alone DURING a RESET rather than setting it to 1 Thus on an edit pattern it becomes possible to WC_WI_NEXT% = NEXT_FIELD WC_MV_NEXT% = "@" : WC_MV% WC_AMV_ACTION% = 4 WC_RESET% = 4 (Volume 3 Issue 5 Page 10) |
Page last modified: 08/02/03