System services

System services

This document describes the order by which event handlers fire in Nexaweb application user input components in general and for Nexaweb application UI's utilizing an Input Method Editor (IME), which allow users to input East Asian language characters.

The following sections outline user input scenarios and the order of events that fire in each of these scenarios for general Nexaweb applications and for Nexaweb application's utilitzing an IME.

Scenario 1

  1. Click on a textField.

  2. Type a single character: a or あ

  3. Click on another component.

The following table lists the events that the application fires for Step 1:

Application

Application With IME

onMouseOver

onMouseOver

onMouseMove

onMouseMove

onMouseDown

onMouseDown

onActiveGained

onActiveGained

onMouseDrag

onMouseDrag

onMouseUp

onMouseUp

The following table lists the events that the application fires for Step 2:

Application

Application With IME

onKeyDown

onKeyUp

onKeyChar

 

onTextChange

 

onKeyUp

 

The following table lists the events that the application fires for Step 3:

Application

Application With IME

onBeforeActiveLost

onKeyUp

onEdit

onTextChange

onActiveLost

onEdit

 

onActiveLost

Scenario 2

  1. Click on a textField.

  2. Type a single character a or あ.

  3. Press the Enter key.

  4. Press the Tab key.

Note: Events for Steps 1 and 2 in this scenario are the same as listed above for Scenario 1,
          Steps 1 and 2).

The following table lists the events that the application fires for Step 3:

Application

Application With IME

onKeyDown

onTextChange

onCommand

onKeyUp

onKeyChar

 

onKeyUp

 

 The following table lists the events that the application fires for Step 4:

Application

Application With IME

onBeforeActiveLost

onBeforeActiveLost

onKeyDown

onKeyDown

onEdit

onEdit

onActiveLost

onActiveLost

Note: If you set the text attribute programmatically, this cancels any onTextChange or onEdit events.