| Viewer |
| VERBatim - V65 |
| QTIPS - Using INIT.VIEW with Printers |
| REVMEDIA Revisited |
| QTIPS - Sub-Headings in RLIST (Revisited) |
| Reader's Clinic - Template Name at Pre-Init |
| Video Control |
| Viewer |
| QTIPS - Using INIT.VIEW with Printers |
| @ATTACK - @View.Mode |
| A RevTI Techie Replies - Mike Pope - Revelation Technologies (UK) Ltd |
| QTIPS - Command Line Options |
| QTIPS - Invalid Code and Command |
| QTIPS - Code/Command Help |
| Utility Diskette # 4 |
| Viewer |
| QTIPS - Using INIT.VIEW with Printers |
| REVMEDIA Revisited |
| QTIPS - Sub-Headings in RLIST (Revisited) |
| Reader's Clinic - Functions and Subroutines |
| Argument passing - Subroutines and Functions - Mike Pope |
| RTP Series - RTP17 |
| QTIPS - PERFORM Arguments and FMT Specifications |
| What's New (and un(der)documented!) In 2.12 |
RevMedia FKB
| Document | V1I6A4 |
| Title | Viewer |
| Keywords | VIEWER RLIST INIT.VIEW @VIEW.MODE HEADING |
| Text | One of the most common "Reader's Clinic" questions is "how to write reports which can page up/page down like RLIST in 1 1+" This feature is one of the most attractive recent features and is so easy to use In any program which sequentially processes records and/or prints lines to the monitor the functionality of the VIEWER window can be invoked by simply includuing the lines CALL INIT VIEW(n) and @VIEW MODE 1 where n is the width of screen required Thus in a simple EXAMPLE program CALL INIT VIEW(40) @VIEW MODE = 1 HEADING "Test Report 'LL'" FOR X = 1 TO 100 PRINT "Testing INIT VIEW" NEXT Patrick Collins of Softsolve Computer SYSTEMS and I had some fun WITH this in trying to work out why the attribute settings seemed to go haywire when using this The answer turned out to be very easy the HEADING command must go AFTER the SETTING of INIT VIEW not before There still seems to be a problem WITH CALLING this sort of program as a subroutine though we'll investigate this further and if we find a fix we'll document it later The fix currently suggested by the support line at RevTech is "don't use it in subroutines" which has a certain logic to it just execute the report program instead (Volume 1 Issue 6 Page 6) |
Page last modified: 30/01/03