-
Alexia Death authored
Don't consider the scan complete unless theres at least MIN_ROWS recorded or very long blank read occurred. Typical problem spot: one brief touch before starting the actual scan. Happens most commonly if scan is started from before the first joint resulting in a gap after the inital touch. http://lists.reactivated.net/pipermail/fprint/2009-December/001406.html
25161286
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| drivers | ||
| nbis | ||
| Makefile.am | ||
| aeslib.c | ||
| aeslib.h | ||
| async.c | ||
| core.c | ||
| data.c | ||
| drv.c | ||
| fp_internal.h | ||
| fprint-list-hal-info.c | ||
| fprint-list-udev-rules.c | ||
| fprint.h | ||
| gdkpixbuf.c | ||
| imagemagick.c | ||
| img.c | ||
| imgdev.c | ||
| poll.c | ||
| sync.c |