libfprint/doc
Benjamin Berg 4d5c34e11a Introduce an early reporting mechanism for verify and match
It is a good idea to report match results early, to e.g. log in a user
immediately even if more device interaction is needed. Add new _full
variants for the verify/identify functions, with a corresponding
callback. Also move driver result reporting into new
fpi_device_{identify,verify}_report functions and remove the reporting
from the fpi_device_{identify,verify}_complete calls.

Basic updates to code is done in places. Only the upekts driver is
actually modified from a behaviour point of view. The image driver code
should be restructured quite a bit to split the reporting and only
report completion after device deactivation. This should simplifiy the
code quite a bit again.
2020-01-13 14:37:39 +01:00
..
xml meson: Use more meson's project_name() 2019-12-17 14:38:19 +01:00
advanced-topics.xml lib: Major rewrite of the libfprint core and API 2019-11-20 11:03:09 +01:00
getting-started.xml lib: Major rewrite of the libfprint core and API 2019-11-20 11:03:09 +01:00
intro.xml docs: Update links to new website 2018-06-03 00:31:05 +02:00
libfprint-docs.xml lib: Major rewrite of the libfprint core and API 2019-11-20 11:03:09 +01:00
libfprint-sections.txt Introduce an early reporting mechanism for verify and match 2020-01-13 14:37:39 +01:00
libfprint-sections.txt-new-manual cleanup: Use FPI prefix for all the internal enum types 2019-12-17 14:38:19 +01:00
meson.build cleanup: Remove fp_internal.h and update drivers_api.h 2019-12-17 14:38:19 +01:00