Limitations with Events (Mobile Module)
VI Events
The Mobile Module supports the following VI events:
You can use the VI key events to capture button input.
Only the ScanCode and VKey event data fields are returned. A scan code is a device-dependent number that identifies a key on the keyboard or a button on the device. A virtual-key code is a device-independent number that identifies a key on the keyboard or a button on the device. The Windows Mobile operating system uses a core set of virtual-key codes that are common for all keyboards. A keyboard driver translates the scan code to a virtual-key code.
 | Note The scan code always returns 0 on devices running Windows Mobile, but the virtual-key code contains valid data. Emulators do not have the issue of the scan code always returning 0. |
The Windows Mobile OS maps some of the buttons on a Mobile target to certain applications, for example, a calendar application. The Mobile Module does not modify these mappings when you use key events.
Control Events
The Mobile Module supports the following Control events:
- Value Change
- Mouse Down (supported only for picture controls)
- Mouse Move (supported only for picture controls)
- Mouse Up (supported only for picture controls)
Stylus Events
The Mobile Module does not support direct stylus events. However, you can use the Mouse Up, Mouse Down, and Mouse Move events in a picture control to capture stylus events.