Symbologies Enumeration - Socket ScanAPI Reference Manual

Socket ScanAPI Reference
ESKT_UNABLEDELETEFILE
ESKT_UNABLEDELETEDIRECTORY
ESKT_UNABLEREADMODEMSTATUS
ESKT_UNABLEGETCLASSDEVICES
ESKT_UNABLEGETDEVICEINTERFACE
ESKT_FILENOTFOUND
ESKT_FILEACCESSDENIED
ESKT_UNABLEREADHIDINFO
C/C++:
The error codes are defined in the SktScanErrors.h file.
Java:
The error codes are defined in
com.SocketMobile.ScanAPI.SktScanErrors.
C#:
The error codes are definied in
ScanAPI.SktScanErrors.
Objective C:
The error codes are defined in the SktScanErrors.h file.

16 Symbologies Enumeration

This paragraph explains how the current set of supported symbologies can be
enumerated from a connected scanner.
The symbology status has 3 states; enable, disable and not supported. The enable
state indicates the device does support this symbology and it is active. The disable
state indicates the device does support this symbology but it is de-activated. The
third state, not supported, means this symbology is not supported by the device.
The symbology is identified in ScanAPI by a Symbology ID. The
kSktScanSymbologyLastSymbologyID is actually not a symbology but instead
indicates the number total of symbologies supported in ScanAPI (this value could
change with different versions).
A symbology status is retrieved by using the Get API with a
kSktScanPropIdSymbologyDevice property as described in this document.
© 2013 Socket Mobile, Inc.
-56L
-57L
-60L
-61L
-62L
-63
-64
-70L
129/152