Psion Teklogix 7527S User's Guide Page 194

  • Download
  • Add to my manuals
  • Print
  • Page
    / 262
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 193
Chapter 20: Trigger Control
Virtual Key Codes
182 Psion Teklogix Mobile Devices SDK Developers Guide
Keyboard trigger sources start at 256—0x100. The trigger source ID for a specific key is 256 plus
the virtual key code. See “Keyboard Remapping” on page 56
for information on virtual key codes.
For example the virtual key code for the [F1] key is 40. So the trigger source ID for the [F1] key is
296; the sum of 256 and 40.
20.4.1 Virtual Key Codes
See the following for a list of virtual key codes:
C++: PsionTeklogix::Keyboard::Key enumeration
Java: com.teklogix.keyboard.VirtualKey class
.NET: PsionTeklogix.Keyboard.Key enumeration
20.5 Trigger Associations
In order to receive trigger events, a trigger consumer must be associated with one or more trigger
sources. Some hardware components should not be operated simultaneously, due to their heavy
power consumption. For example, an internal imager and a tethered RFID reader should not be
scanning at the same time. Doing so may cause the terminal to spontaneously turn off due to insuf-
ficient power.
Before being associated with the trigger source, the trigger consumer must register to receive
trigger events. Only the trigger consumers associated with a specific trigger source receive events
originating with that trigger. Several consumers can be associated with the same trigger source.
When a trigger consumer is deregistered, all its trigger associations are deactivated. If the trigger
consumer re-registers the associations are re-activated.
Each development language provides API elements that associate a trigger source ID with a
trigger consumer.
20.5.1 Trigger Control Flags
Trigger control flags modify a trigger association. These flags are specified when a trigger associ-
ation is created. Several trigger control flags can be set during one trigger association attempt.
Unless the temporary flag is set, all trigger associations are permanent and persist across both
warm resets and cold resets. It is recommended that unless the application is launched at system
startup, the temporary flag be set for all trigger associations.
Exclusive flag: Setting this flag ensures that only one trigger consumer is associated with a trigger
source. If this flag is set during an attempt to create a trigger association, the following can occur:
If there is no existing trigger association for the trigger source, the association is successful
and all further attempts to create an association for this trigger source fail until this exclusive
association is deleted.
If there is an existing trigger association for the trigger source, this attempt to create an exclu-
sive association fails.
Override flag: When this flag is set during an attempt to create a trigger association, all existing
trigger associations for the trigger source are replaced by the new one. Even an exclusive trigger
association is replaced.
Temporary flag: When this flag is set, the trigger association does not persist across either a
warm reset or a cold reset. If the override flag is also set, then the previous trigger association for
the trigger source is restored when this association is deleted, or the trigger consumer is deregis-
tered. Only one temporary-plus-override flag can be in existence for each trigger source.
Page view 193
1 2 ... 189 190 191 192 193 194 195 196 197 198 199 ... 261 262

Comments to this Manuals

No comments