Hi, Daniel
I have two questions:
1. Maybe it will be better if libfprint will support different storages
directly? Is there any special reason to move this functionality to the
fprintd?
2. Is there any docs for async API? If I understand correctly, user of async
API should use following scheme, am I right?
fp_async_open_dev();
fp_get_pollfds();
//setup timeout, struct pollfd, etc
//identify will call callback passed to it, this callback will
//set need_again to 0
need_again = 1;
fp_async_identify_start();
again:
ret = poll();
if (ret > 0) {
fp_handle_events();
}
//do some app-specific stuff here
if (want_stop) fp_async_identify_stop();
if (need_again) goto again;
fp_async_close_dev();
_______________________________________________
fprint mailing list
[email protected]
http://lists.reactivated.net/mailman/listinfo/fprint
