![Ubisys 7047 Скачать руководство пользователя страница 44](http://html2.mh-extra.com/html/ubisys/7047/7047_reference-manual_3150151044.webp)
44
www.ubisys.de
9.2.5.1.
Constructor
CSmartCardStatusListener(CSmartCardContext &context);
Constructs the instance in the given context. Please note that the context must be valid during the
overall lifetime of this instance.
9.2.5.2.
Methods
bool
GetStatusChange(CSmartCardStatusReceiver ¬ify, DWORD dwTimepout = INFINITE);
Get status changes. Waits until a status change has occurred or the specified timeout has elapsed.
Detected Events will be passed to the relevant methods of the specified class instance (derived from
CSmartCardStatusReceiver).
9.2.6.
CSmartCardExceptionHelper
The API uses exceptions to propagate unexpected error conditions, e.g. transmission problems.
It is left at the user’s discretion, which exception class should be thrown. Two default implementations
are provided. One class is derived from the C++ standard library class std::exception, whereas the
other one is derived from the MFC CException class and can be used in MFC programs.
Please note that MFC exceptions must be caught by pointer, whereas ordinary C++-exceptions are
usually caught by (const-) reference (or less-optimal by value).
CSmartCardExceptionHelper is a helper class, which provides static methods to throw an exception as
well as methods to translate error codes returned from the Smart Card API.
9.2.6.1.
Local Definitions
A enum is defined, enumerating the most common errors. Translation from error codes returned by the
Smart Card API to this enum is done internally by the (private) static method
MapErrorCause().
enum
{
errorUnknown, // Unknown error, no mapping exists
errorNoCard, // No card in reader
errorTransmission, // Transmission failed
errorInvalidParameter, // Invalid Parameter
errorUnknownReader, // Reader not known
errorTimeout, // A timeout occurred
errorSharing, // A sharing violation occurred
errorProtocolMismatch, // Protocol mismatch
errorUnavailable // Reader or card/tag not available
};
A sharing violation occurs if two applications try to open the same reader with incompatible settings,
e.g. another application opened the reader in exclusive mode.
Содержание 7047
Страница 1: ...13 56 MHz RFID USB READER REFERENCE MANUAL...
Страница 28: ...28 www ubisys de...
Страница 34: ...34 www ubisys de...
Страница 37: ...37 www ubisys de Figure 4 Acknowledging the Warning Notice Step 2 Step 2 Acknowledge the warning message...