Pavel Herrmann wrote: > Well, empty in any way, something that could be used as "print not > enrolled" in scenario with the same number of fingers for each account > (something like 10 for human beings) so that the back-mapping is not > required. Theoretically something that will always being identified > against, maybe some number of zeros. (NULL pointer is not usable as it > is used as the last element in the array, if I remember well)
I don't know whether you're asking about existing libfprint API or dreaming up a new one, but existing libfprint API has no way to load multiple fingerprints from a file. Glossing over the simplistic storage method (which is too basic for your needs), the advanced API takes a binary blob and converts it into print data. It doesn't know or care where the binary blob came from: file, thin air, or otherwise. So if you have users without enrolled fingerprints, thats your problem to deal with, not the library's. > PS. for the dependency suggestion in the other thread, why do we have > (extended) USE in gentoo? there are LIRC_DEVICES and VIDEO_CARDS and > many others, why no FPRINT_DEVICES? I will try to have a look at this > one in the next week. As noted in that thread there is currently no way to include or exclude drivers from compilation. Daniel _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
