Hi, Has anybody had a chance to take a look at this patch?
I'd be interested in feedback and information about how to get it applied. >> Is there a way for "scanimage --batch-prompt ..." to poll the button on >> the front of the scanner instead of waiting for RETURN? >> >> In gscan2pdf I can see the button sensor activate when I press the >> button (and refresh the scanner list with the button held down) but I >> can't see it in xsane or with "scanimage -A". >> >> I'm happy to start the program manually (rather than using scanbd or >> scanbuttond) but it'd be nice if I can then just load the hopper and >> press the button on the scanner for each batch. >> >> Maybe it would be better to have a scanimage option which just blocks >> until the button (chosen with command line flags?) is pressed > > Please find a patch to scanimage.c attached. > > This patch adds the "--sensor-trap" and "-s" options. > > With no arguments this option prints the status of all the sensors as > per the "-A" option. When the name of the sensor is given as the option > argument it waits for that sensor to change state before proceeding as > normal. i.e. it scans with the supplied options unless "-n" is present, > in which case it exits with success. > > I have tested this on the Fujitsu ScanSnap iX500. > > With the "--sensor-trap=scan" option it waits until the button up event > on the front panel button before proceeding (provided the button is not > held down when scanimage is run). > > With the "--sensor-trap=page-loaded" option it waits for a piece of > paper to be placed in the hopper before immediately scanning it. > Interestingly, if the hopper contains a piece of paper when scanimage is > invoked then it immediately scans it otherwise it waits until the page > is inserted and then scans it. I'm not sure if this will be the case for > all scanners. > > > There are a couple of issues that might require further attention: > > I'm not sure if the signal handler initialisation is in the correct > place: If I Ctrl-C the binary whilst it is waiting for the state change > then it can't stop the scanner on the first try and aborts on the second. > > I'm not sure if the indenting or function signature styles are correct. > > > > > Regards, > @ndy > > > Regards, @ndy -- [email protected] http://www.ashurst.eu.org/ 0x7EBA75FF -- sane-devel mailing list: [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
