Top |
void | fpi_print_add_print () |
void | fpi_print_set_type () |
void | fpi_print_set_device_stored () |
gboolean | fpi_print_add_from_image () |
FpiMatchResult | fpi_print_bz3_match () |
gchar * | fpi_print_generate_user_id () |
gboolean | fpi_print_fill_from_user_id () |
void fpi_print_add_print (FpPrint *print
,FpPrint *add
);
Appends the single FPI_PRINT_NBIS print from add
to the collection of
prints in print
. Both print objects need to be of type FPI_PRINT_NBIS
for this to work.
void fpi_print_set_type (FpPrint *print
,FpiPrintType type
);
This function can only be called exactly once. Drivers should call it after creating a new print, or to initialize the template print passed during enrollment.
void fpi_print_set_device_stored (FpPrint *print
,gboolean device_stored
);
Drivers must set this to TRUE
for any print that is really a handle
for data that is stored on the device itself.
gboolean fpi_print_add_from_image (FpPrint *print
,FpImage *image
,GError **error
);
Extracts the minutiae from the given image and adds it to print
of
type FPI_PRINT_NBIS.
The image
will be kept so that API users can get retrieve it e.g.
for debugging purposes.
FpiMatchResult fpi_print_bz3_match (FpPrint *temp
,FpPrint *print
,gint bz3_threshold
,GError **error
);
Match the newly scanned print
(containing exactly one print) against the
prints contained in template
which will have been stored during enrollment.
Both template
and print
need to be of type FPI_PRINT_NBIS for this to
work.
gchar *
fpi_print_generate_user_id (FpPrint *print
);
Generates a string identifier for the represented print. This identifier encodes some metadata about the print. It also includes a random string and may be assumed to be unique.
This is useful if devices are able to store a string identifier, but more
storing more metadata may be desirable. In effect, this means the driver
can provide somewhat more meaningful data to fp_device_list_prints()
.
The generated ID may be truncated after 23 characters. However, more space is required to include the username, and it is recommended to store at at least 31 bytes.
The generated format may change in the future. It is versioned though and decoding should remain functional.
gboolean fpi_print_fill_from_user_id (FpPrint *print
,const char *user_id
);
This is the reverse operation of fpi_print_generate_user_id()
, allowing
the driver to encode some print metadata in a string.
FpPrint to fill metadata into |
||
user_id |
An ID that was likely encoded using |