RTP Series - RTP42
RTP Series - RTP51
Reader's Clinic - AREV Runtime
@ATTACK - @PDisk.On
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
AREV Comes to Czechoslovakia Les Palenik, Cosmotron Systems
Utility Diskette # 4
Version 3 Technical Highlights - Customising NewApplication Creation
@ATTACK - @Macro.Words
Version 2
Directory Exists on Novell
Gas Bar
Prompt Help
DOS Interfacing (Part II)
@ATTACK - @Help.Level
@ATTACK - @StatList
QTIPS - Standardising Error Message Display
Video Control
Customising the Status Line
QTIPS - Command Line Options
Customising the Status Line
VERBatim - V86
@ATTACK - @Help.Level
@ATTACK - @Window.Level
Reader's Clinic - Functions and Subroutines
Reader's Letters - Jim Owen
Playing with Scan Codes
Argument passing - Subroutines and Functions - Mike Pope
Customising the Status Line
Prompt Help
QTIPS - Improved Menu Help 1
QTIPS - Improved Menu Help 2
@ATTACK - @Macro.Hex
Playing with Scan Codes
Uncommon Knowledge - WC_Detail_Help%
Uncommon Knowledge - WC_Protect_Help%
Creating Your Own Background Processes
@ATTACK - @Last.Select.Process
Reader's Forum
QTIPS - Menu Item Pre-Processing
Gas Bar
Prompt Help
@ATTACK - @CrtMaxHigh
@ATTACK - @Modal
@ATTACK - @Status.On
Window or Not?
REVMEDIA Revisited
Utility Diskette # 4
Reader's Clinic - Incorrect Indexes
Vroom
RTP Series - RTP20
RTP Series - RTP12
Form.List.S
VERBatim - V5
@ATTACK - @Last.Select.Process
@ATTACK - @Save.Select
QTIPS - File Variable of File In SELECT Statement
QUERY.SUB
REVMEDIA Revisited
QTIPS - Extended Select Syntax
Spindex - A Review
Spindex vs BondTRV
REVMEDIA Revisited
QTIPS - Replacing GAS.BAR routine during PERFORM "SELECT"
QTIPS - Extended Select BY
QTIPS - EasyWriter
QTIPS - MFS - Select.Index
Set_Attach_Sub and Attach Images
Vroom
RTP Series - RTP32
Utility Diskette # 3 - Part I
Utility Diskette # 4
Utility Diskette # 3 - Part I
Utility Diskette # 3 - Part II
Reader's Clinic - Incorrect Indexes
Redisplaying Multi-Values
RTP Series - RTP21
Bugs and PCs - MultiValued Keys on Windows
Reader's Clinic - Slow Multivalued Screen Display
RTP Series - RTP27
QTIPS - Printing Large Variables from the Debugger
VERBatim - V87
Utility Diskette # 4
VERBatim - V15
QTIPS - Compiling Work around on runtimes
Reader's Clinic - EVAL
QTIPS - Compiling Protection Code
RTP5 and RTP51
Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd)
VERBatim - V26
RTP Series - RTP49
VERBatim - V18
QTIPS - Amending non-Attached Files
Set_Attach_Sub and Attach Images
Bugs and PCs - Macro Keys
QTIPS - SET.MACROS - Choosing Active Macro Set
QTIPS - TCL Disabled
Reader's Clinic - Functions and Subroutines
Argument passing - Subroutines and Functions - Mike Pope
Utility Diskette # 3 - Part II
Reader's Clinic - Slow Multivalued Screen Display
@ATTACK - @Modal
Redefining Keys
Background Processing
Reader's Clinic - Prompting for Passwords
Capture
Creating Your Own Background Processes
@ATTACK - @Edit.Keys
@ATTACK - @Index.Time
@ATTACK - @PlayBack
@ATTACK - @Priority.Int
How Indexes Are Updated
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
QTIPS - Use of Mouse
QTIPS - Interrupt Proof Error Messages
Uncommon Knowledge - WC_Soft_Keys%
A RevTI Techie Replies - Mike Pope - Revelation Technologies (UK) Ltd
Version 3 Technical Highlights - Input.Char
Version 3 Technical Highlights - @Prog.Char
Version 3 Technical Highlights - Highlight
Vroom
RTP Series - RTP32
Utility Diskette # 3 - Part I
VERBatim - V16
Popups
Utility Diskette # 3 - Part I

RevMedia FKB

DocumentV4I4A4
TitleCustomising the Status Line
KeywordsSTATUS
LINE
SYS.TEXT_PARMS
TextImages
When designing applications WITH an AREV "look and feel" it can be desirable
to create highlighted words on the bottom status line (as WITH the system
help level 2 function keys) In addition when indicating CURSOR key
movement it makes sense to use the arrow characters to illustrate the keys
to press rather than spelling out "Cursor Left" "Cursor Right" etc

Two minor points need to be made before the explanation proper begins
Firstly Status Line images are now stored in SYS TEXT_PARMS WITH a key of
Process*Status (or Process2*Status for help level 2 images) Secondly there
are now only two supported help levels 0 and 2 Whilst it is possible to
use a help level of 1 this can lead to PROBLEMS

When adding new status line images it behoves us to cater for both levels of
user so two status line images should be created per process one for level
0 and one for level 2 Statup will automatically select the correct image
when asked to load Process This discussion will concentrate on level 2
status images but it can be amended for level 0

The LAYOUT of the status line image is documented in various places (UTILITY
subdirectory on pre release 2 0 Programmer's Reference on 2 1 System
Subroutines book) but the field that is of interest when customising
highlighted words is field 2 This field (in a level 2 status line)
contains four MULTIVALUES three for the top three boxes of the status line
and the fourth for the bottom line Highlighted words can only be put into
the fourth multivalue

Very Simple Program to Test Amended Status Lines
So that the new status lines can be tested a simple program such as the one
following can be used Simply compile catalog and attach to a macro key

Subroutine TestStat
/*
Note that WITH help level 2 this will display record SPREZZ2
*/
Call Statup(4 "SPREZZ" Save)
Call Input Char(x)
Call Statup(5 "" Save)
Return

Adding Highlighted Words
The key point here is the use of hyphens In multivalue 4 everything up to
the first hyphen will be highlighted then AFTER the first hyphen every
word before a hyphen will be highlighted Thus if a record were created
called SPREZZ2*STATUS WITH a LAYOUT as follows

MENU
SprezzżRevM żField 3żThis is Highlighted This Isn't ThisIs This Isn't
1

it would appear on the status line as follows

³Sprezz³RevM ³Field 3 ³
ĆÄÄÄÄÄÄĮÄÄÄÄÄÄĮÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ“
³This is Highlighted This Isn't ThisIs This Isn't³

Note then that to give the illusion of multiple words being highlighted
mixed capitalisation must be used (I E ThisIs rather than This Is where
only the Is would be highlighted) Note further that when the text in
the record is shorter than the WIDTH of the status line cell a number of
spaces must be appended AFTER the text to display to the width of the cell
With the final cell this can be made easier by appending a VALUE MARK

Adding Arrow Characters To the Status Line
Unfortunately the ASCII characters for the various arrow symbols cannot be
added DIRECTLY into the status line as they cause the SCREEN to become
corrupted To get around this a fix has been provided It would not be
uncharitable to describe this fix as a kludge

Essentially five characters have been provided that are taken by the system
to mean that they should be replaced WITH arrow characters when they are
bracketed by *'s and a flag VARIABLE is set The characters and their
meanings are as follows

# Ž (represents a double headed arrow)

~ 

|