Instructions

U.are.U SDK - Developer Guide 73
OPOS
Getting Device-Specific Information with DirectIOEvent
The DirectIOEvent event is fired by a Service Object to deliver vendor-specific events to the application. The U.are.U
JavaPOS API uses DirectIOEvent events to notify the application about device connection and disconnection and
intermediate events such as finger touch or removal.
This chapter contains specific information about the U.are.U SDK implementation of the OPOS Control.
DataEvent
Syntax
<< event >> upos::events::DataEvent
Status: int32 { read-only }
Description
This event is fired to provide input data from the fingerprint reader to the application. The actual input data is placed in
one or more device-specific properties.
Attribute
This event contains the following attribute:
DirectIOEvent
Syntax
<< event >> upos::events::DirectIOEvent
EventNumber: int32 { read-only }
Data: int32 { read-write }
Obj: object { read-write }
Description
This event is fired by the Service Object (SO) to communicate directly with the application. DirectIOEvent is used in
the U.are.U SDK to notify the user of the image-capturing status, fingerprint reader connection status, and image
quality, etc., whenever required.
Attributes
This event contains the following attributes:
Attribute Type Description
Status int32 BIO_DATA_ENROLL if enroll capture is completed.
BIO_DATA_VERIFY if verify capture is completed.
Attribute Type Description
EventNumber int32 Event number whose specific values are assigned by the SO.
Data int32 Additional numeric data. Specific values vary by the EventNumber and the SO.
Obj object Additional data whose use varies by the EventNumber and the SO.