Reader's Clinic - Capture Command and Captured Keystrokes
Catalyst
Popups
Catalyst Tips
QTIPS - NoRead
Reader's Clinic - EVAL
QTIPS - New Catalyst Option
A RevTechie Replies
RTP Series - RTP9
RTP Series - RTP50
VERBatim - V25
@ATTACK - @Files
Utility Diskette # 3 - Part I
Playing with Scan Codes
QTIPS - Compiling Protection Code
QTIPS - Invalid Code and Command
QTIPS - Code/Command Help
Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd)
QTIPS - Command Line Options
QTIPS - Invalid Code and Command
QTIPS - Code/Command Help
Utility Diskette # 4
Window or Not ?
Vroom - Window Processing
QTIPS - Window Symbol Tables
VROOM - Window Processing II
@ATTACK - @HW
Uncommon Knowledge - WC_Reset%
Reader's Clinic - Related Windows
Window or Not?
Reader's Clinic - Scribe Replace Processes in Window
Soft Windows
QTIPS - Window Bug and Debugging Window Bug
Overlapping Windows And Window Menus
QTIPS - New Catalyst Option
QTIPS - Collectors on the fly
QTIPS - Blank Menus in Windows
QTIPS - Moving Objects the EASY way.
Creating Your Own Background Processes
@ATTACK - @Last.Select.Process
Reader's Forum
QTIPS - Menu Item Pre-Processing
Reader's Clinic - Functions and Subroutines
Argument passing - Subroutines and Functions - Mike Pope
Reader's Clinic - AREV Runtime
QTIPS - Compiling Work around on runtimes
QTIPS - Runtime Version
@ATTACK - @Modal
Popups
Catalyst Tips
QTIPS - DOS File Names
DOS Interfacing (Part II)
VERBatim - V116
@ATTACK - @Pri.File
@ATTACK - @Rollout.File
File Variables
How Indexes Are Updated
Index Record Layouts
QTIPS - File Variable of File In SELECT Statement
QTIPS - Amending non-Attached Files
LINEAR HASH FILE STRUCTURES - Part 1
Index Flush
QTIPS - File Handle Structure
Utility Diskette # 3 - Part II
Reader's Clinic - Slow Multivalued Screen Display
VERBatim - V17
VERBatim - V6
VERBatim - V125
Utility Diskette # 3 - Part I
Version 3 Technical Highlights - Copying Rows Programmatically
Version 3 TCL Subroutines - Copying Rows
DOS Interfacing (Part II)
Reader's Clinic - Preventing Records Being Amended
How Indexes Are Updated
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
Caching in on the Frames Array - Mike Pope
Vroom
RTP Series - RTP32
Utility Diskette # 3 - Part I
@ATTACK - @Return.Value
Catalyst
@ATTACK - @Ans
QTIPS - Compiling Work around on runtimes
QTIPS - Potential Problem When Using @ANS
Reader's Clinic - Page Marks in Windows

RevMedia FKB

DocumentV2I5A5
TitleCatalyst Tips
KeywordsCATALYST
WC_REGISTER%
POPUP
TextSince our introductory issue Catalyst has had several new features added
Most of these new features have been documented on the Readme files supplied
with the upgrade diskettes Several additional undocumented features still
exist and our thanks go to those who provided the following exciting
features These have all been tested on 2 01 not 1 16

Conditional Execution
If an X is appended to the catalyst code the command will only be executed
if the CURRENT window record has been modified This is most useful on a
pre save routine which will be called regardless of whether modifications
have been made As an EXAMPLE of this try putting "HLX This is a test" on
the Pre Save process of a window

Subroutine CALLS USING Registers
The branches to be passed to a subroutine can be stored in the window
registers and thus modified at runtime by CHANGING the contents of the
registers Thus if WC_Register%(5) were loaded WITH "CLS" and the catalyst
call CALL CATALYST("S" "PROC ") were issued PROC would be called and
passed the parameter CLS One caveat do not use WC_Register%(10) as the
system does not recognise this and uses WC_Register%(0) instead

Modified Popup Calls
Frequently it is desirable to take a popup record FROM file change an
attribute or two and display it without modifying the file copy This can be
tedious A West Coast reader points out that a popup record can be passed in
place of the command WITH a P code and that Catalyst will then display the
record Thus to change the X position for EXAMPLE read in the popup record
(POP_REC) change field one to the desired value (POP_REC<1> = X) and finally
CALL CATALYST("P" POP_REC)

Terminating Catalyst Chains
In issue 1 it was pointed out that catalyst CALLS can be stacked using
semi colons If any of the stacked COMMANDS sets @ANS to 1 the rest of the
commands are not executed (Ask me how I know )


(Volume 2 Issue 5 Page 7)
[revmedia/copyrigh.htm]

Page last modified: 08/02/03