Programmable control events. These are method triggered by an event within the rule set.
Some triggers are user initiate while others occur as a substance of course inside the rule set procedure.
Nucleus event triggers have two main types:
- ID event triggers: ID triggers occur in relation to the controlling key (iconv, genid) and the rule set as a whole which include compile, load, postread, prewrite, postwrite, predelete, etc.
- Field event triggers: Field triggers take place during processing of exact field objects and include prefield, post field, justification, input and output conversion.
Triggers include:
- Initialization
- Rule Compile Time
- Help event
- Console/ATGUI Hot spot or button
- Rule Load Time
- Item Post-read
- Display correlative
- Pre-Field processing
- Input conversion
- In-field processing
- Output conversion
- Post-Field
- Pre-File
- Post-File
- Post-Delete +
- Special (jump) commands
- Validation
- Exit time
- Messaging
- Choice or pop-up selection
- Record ID generation
- Field Delete
- Input Timeout
- Post-Column-Sort
- KeyIn event
- Cross Page (NuForm ONLY!)
- Unload
- Pre-delete
- Wrap up
- Commandmenu
+ indicate an event which is a “sub event”, i.e. part and parcel of one more event classification and needy upon user interaction.
Incorporating an event Trigger
To incorporate an event "Trigger", an events call or trigger event necessity be defined in the suitable area within the Screen dictionaries. SCRDICTS are defined within WINMAINT either by a JUMP from the Nucleus script to the Screen dictionary or by selecting the "Screen dictionary" option from the WINMAINT menu.
- Defining properties
- Options
Event code
In order to process a Nucleus event, the programmer may use also access-like codes or call a modified subroutine.
For expediency and in order to keep all modified events code in a single place, a widespread event subroutine is created when a script is compiled. The sweeping subroutine is the optional place for storage of occasion methods.
The default naming convention is:
SUBS.ScreenName,
Where ScreenName is the name of your screen created using the WINMAINT development environment. The subroutine SUBS.ScreenName, is created by WINMAINT in the file called ISUB, in the data area ISUB, S.
The SUBS item can be modified by:
- Jump from an associated trigger event
- Using source code control, edit the item, as:
- USC ISUB,S SUBS.ScreenName
- From Winmaint, select edit Subroutine