New GUI Events

This Release introduces some additional GUI events.

Note: Screen shots and more detailed information will be provided as these details are finalized.

Overview:

You can now be notified when a user tabs into, out of, or changes the value in a field. This is controlled by three new attributes on the GUI Attributes screen: Tab In / Tab Out / Value Changed. These are Y/N fields you can set to be notified when these events occur. This will allow you to make your processes much more interactive, you will not have to wait until the user presses Enter to interact with the image.

Runtime

if you set any of these attributes on a field, then --- OPTION will be set according to what has happened. If the user tabbed into a field, then --- OPTION will be set to TAB IN and --- CURSOR AT FIELD will contain the name of the field the user tabbed into. If the user tabbed out of the field, then --- OPTION will be set to TAB OUT and --- CURSOR AT FIELD will be set to the next field they tabbed into (but probably should be set to the field they tabbed out of). If the field value changed, then --- OPTION will be set to VALUE CHANGED and ---- CURSOR AT FIELD will contain the name of the field that was changed.

Note that only the Option Intercept event point will be executed for these values of --- OPTION, unlike running an Optional Child, which will normally run Option Intercept, Pre/Post Invocation, and all the frames preceeding the current frame.

The Value Changed event will only be triggered if the user changes the field and valueChangedTimer (in Client Preferences) has expired. For example, if valueChangedTimer is set to 1000 ms (1 second) and the user changes the value in the field, the event will only fire if they remain in the field for 1 second. If they tab out to another field, then the value changed event does not fire (Bug?). This event may fire more than once for a field if the user changes it again after the event has fired and does not tab out before the timer expires.