Interactive trigger for handling changes to the content of an edit box as the user
types, when the OnEdit widget property is
True. The onEdit
trigger is typically used to implement incremental search functionality, in which the retrieved
results change as the user enters a search profile.
; <Your code here>
end ; trigger copyTo
|Form widgets: EditBox
| Activated if the OnEdit property is
True when the user changes the field content.
|Behavior upon completion:
The onEdit trigger has no parameters. Unlike most interactive triggers, an empty trigger definition is not added to each newly-created edit box field. Instead, you must manually define it yourself. (The edit box is the most commonly-used widget, and this prevents unused code from being added to all these widget definitions.)
The onEdit trigger is applicable to both single-line and multiline edit boxes. In a multiline edit box, the trigger is not fired if the field is empty and the Enter key is pressed.
The trigger can be fired each time the user
changes the content of the field in some way—by adding or removing a character, or by pasting and
cutting content, or after a delay of 200 milliseconds. However, the
onEdit trigger is not fired if
the field is assigned a value in ProcScript.
To prevent unnecessary processing, the trigger can
be fired only if the OnEdit property is
EditDelay property can be used to apply a delay of 200 milliseconds after the
user stops entering data. This reduces the frequency of firing the onEdit trigger to improve
performance when retrieving data. By default, EditDelay is
Example: Incremental Searching
The following example shows how you can implement a simple form of incremental searching. The form contains two entities—CUSTOMER and CUSTOMER_FILTER. The following onEdit trigger is implemented on the NAME.CUSTOMER_FILTER field:
trigger onEdit variables string vSearchProfile endvariables clear/e "CUSTOMER" vSearchProfile = "%%NAME.CUSTOMER_FILTER%%%•*" NAME.CUSTOMER = $uppercase(vSearchProfile) retrieve/e "CUSTOMER" end; onEdit trigger
- Clear the CUSTOMER entity.
- Create a search profile using the value of the NAME.CUSTOMER_FILTER field.
- Assign the search profile to the field to be searched (converting it to uppercase).
- Retrieve the CUSTOMER occurrences that match the search profile.