Joshua N Pritikin wrote:
I must be missing something really basic. Why is enum fp_finger part of
the API? Do people actually enroll all their fingers? If they do, why?
It's a design choice, intending that you ask the user to scan a specific
finger. It doesn't mean you have to enroll all your
I must be missing something really basic. Why is enum fp_finger part of
the API? Do people actually enroll all their fingers? If they do, why?
It seems to me that I want to be identified by a single finger for most
applications. Perhaps for high security, it would be worth testing more
than
I must be missing something really basic. Why is enum fp_finger part of
the API? Do people actually enroll all their fingers? If they do, why?
It seems to me that I want to be identified by a single finger for most
applications. Perhaps for high security, it would be worth testing more
than
Joshua N Pritikin wrote:
I must be missing something really basic. Why is enum fp_finger part of
the API? Do people actually enroll all their fingers? If they do, why?
It seems to me that I want to be identified by a single finger for most
applications. Perhaps for high security, it would
On Thu, Sep 24, 2009 at 02:43:46PM +0100, Simon Kenyon wrote:
Joshua N Pritikin wrote:
I must be missing something really basic. Why is enum fp_finger part of
the API? Do people actually enroll all their fingers? If they do, why?
It seems to me that I want to be identified by a single
