Def Trigger n

Trigger set definitions declare what type of emulator elements are targeted, and the individual triggers themselves refer to these elements. The given number is strictly arbitrary in order to provide uniqueness in the entry, and is thrown away. Using the caret symbol as a field separator, the following tags and content apply to the overall definition of the trigger set. These tags are not case-sensitive:

• Group – The group number, which is used in the case of switching to different modes. The only required group number is number one.
• Style – The style number declares the type of text that is pulled, in order to use for testing conditions in the associated triggers within the group. The following style numbers have defined effects:
  • 1) This style number declares the triggers to refer to windows.
  • 2) If the targeted windows change their display status from minimized or non-existent, to visible (maximized or normal size), then the status-changed window is re-targeted. Otherwise any of the other targeted windows that are visible are targeted.
  • 3) This style number declares that, while any one of the listed trigger definitions in the group is found to exist, then HostSearch is to remain idle (a type of Reverse Trigger). This type of trigger style can be employed to pause screen scraping until the user deals with a modal input window. The concept behind this functionality is that screen scraping can continue once the user has taken the action or clarification that the legacy system requires. If any of the triggers defined for the group is identical to a Group 1 trigger, then the Group of this trigger definition must also be 3.
• Line - The full line of text in the emulator for the given line number is extracted.
• Title - A part of the window title is extracted. The format of a Title specification is: offset+length. For example, “13+8” extracts up to eight characters, beginning with the 13th character.
• Block - A part of the window content is extracted. The format of a Block specification is: row,col+length. For example, “6,13+8” extracts eight characters, beginning with the 13th character on row six. A Block instruction is incompatible with a Title instruction.
• Subtext - A subtext instruction is used with a Line or Block instruction. A part of the already-extracted text is extracted. The format is the same as Title: offset+length. Using a Block instruction is more compact, but for those emulators that do not understand Block-oriented instructions but are able to target a full line of text, a Line instruction together with a Subtext instruction results in the same effect.
• Cursor - The cursor must be present at the given coordinates. The format of a Cursor specification is: row,col. This instruction can be employed with other instructions, where the other instructions determine that the screen is correct for triggering, but it is also important that the cursor is on a particular input field. This instruction is especially important when the legacy system remains on the trigger screen to do other work, even after the search is complete.
• UserPage - For those emulators that provide for multiple memory page windows, this tag specifies a page number which is tested against the page that is currently displayed to the user. If the page number matches, then any accompanying block of text specification is extracted against the given page. Using this tag effectively specifies that the defined trigger text must be on the current user display, not on a hidden page.
• WinDef - For those text-based emulators which do not use separate Microsoft Windows frames, but instead display text-based "windows” (where a single text-based window uses graphic borders to simulated embedded text windows), this instruction determines whether the subwindow definitions are correct for triggering. The format for a WinDef instruction is: row,col+ width,height.