Understanding ADC Event Triggers in the Browser

Owned by Darcy Curtin
Jan 28, 2020
1 min read

NLINK ADC screen Events are triggered when the user exits the associated input field or clicks the associated button.

When scanning data into a field, devices should be set to automatically exit the field (generally by sending a Tab) after the scan. This will trigger the NLINK Event.

However, when typing, the user must exit the field manually:

  • The most consistent way to do this is to use the Tab key.
  • Some browsers will also exit with the Enter key.
  • It also works to click the mouse somewhere else on the screen outside of the input field.

Confusion can arise in the following scenario:

  1. User types data into a field that has a configured Event,
  2. and does not exit the field,
  3. and then clicks a Button.

What happens is that the browser understands the click of the button as "clicking the mouse somwhere else on the screen outside of the input field", and thus triggers the NLINK Event associated with the input field. The button Event is not going to be triggered in this case.

Now consider a similar scenario:

  1. User types data into a field that does not have a configured Event,
  2. and does not exit the field,
  3. and then clicks a Button.

In this case, the button Event does trigger, as there is no field exit Event that needs to occur first.