Document Title Here
AET65 API
Version 1.0
idvation GmbH
Otto-Hesse-Straße 19 / T5
Phone +49 6151 9926567
D-64293 Darmstadt
Fax +49 6151 3689296
www.idvation.com
Page 18 of 84
Page 18 of 84
3.3.4.
ABSCapture
ABS_STATUS ABSCapture(
IN ABS_CONNECTION hConnection
IN ABS_OPERATION *pOperation
IN ABS_DWORD dwPurpose
OUT ABS_BIR **ppCapturedTemplate
IN ABS_DWORD dwFlags
)
Description
This function captures sample for the purpose specified and creates
a new fingerprint template from it.
Parameters
hConnection
Handle to the connection to FM.
pOperation
See description of ABS_OPERATION
dwPurpose
A value indicates a purpose of the biometric data capture.
It
can
be
either
ABS_PURPOSE_ENROLL
or
ABS_PURPOSE_VERIFY. ABS_PURPOSE_UNDEFINED is not
allowed.
Note
that
calling
ABSCapture()
with
dwPurpose
set
to
ABS_PURPOSE_ENROLL is obsolete and it is functionally
equivalent to calling ABSEnroll().
ppCapturedTemplate
Pointer which is set to newly allocated template. Caller is
responsible to release the memory with ABSFree.
dwFlags
Bitmask specifying flags, which modify slightly behavior of the
function.
This function supports only flag ABS_FLAG_NOTIFICATION. If it is
set, the verification operation does not show any GUI feedback until
the finger is swiped. This can be useful for applications doing their
own work; and only when user swipes, the application processes
some special action. Until the user swipes, he is not disrupted with
any dialog.
Showing/hiding of the dialog is controlled by messages
ABS_MSG_DLG_SHOW and ABS_MSG_DLG_HIDE.
The flag ABS_FLAG_NOTIFICATION can be used only in case that
dwPurpose is set to ABS_PURPOSE_VERIFY.
Return Value
ABS_STATUS
Result code. ABS_STATUS_OK (0) means
success.
