[sane-devel] sane_cancel()

2008-07-16 Thread Kåre Särs
Hi, I'm a bit confused with the use of sane_cancel(). I noticed today that the pixma backend requires a sane_cancel after each scan (libksane did not work correctly with the pixma backend). I have read here on the list: 5. be aware that a proper front-end in batch mode will call sane_start() at

[sane-devel] sane_cancel()

2008-07-16 Thread Kåre Särs
Hi again, On Wednesdayen den 16 July 2008 02:02:36 K?re S?rs wrote: Hi, I'm a bit confused with the use of sane_cancel(). I noticed today that the pixma backend requires a sane_cancel after each scan (libksane did not work correctly with the pixma backend). I have read here on the list: 5.

[sane-devel] sane_cancel()

2008-07-16 Thread Nicolas
pixma backend can handle batch scan, I've tested it under both xsane and scanimage -b : $ scanimage -b Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 Scanned page 1. (scanner status = 5) Scanning page 2 Scanned page 2. (scanner status = 5) Scanning page 3 Scanned page 3.

[sane-devel] sane_cancel()

2008-07-16 Thread Kåre Särs
On Wednesdayen den 16 July 2008 09:28:49 Nicolas wrote: pixma backend can handle batch scan, I've tested it under both xsane and scanimage -b : $ scanimage -b Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 Scanned page 1. (scanner status = 5) Scanning page 2

[sane-devel] sane_cancel()

2008-07-16 Thread m. allan noah
On 7/16/08, K?re S?rs kare.sars at kolumbus.fi wrote: On Wednesdayen den 16 July 2008 09:28:49 Nicolas wrote: pixma backend can handle batch scan, I've tested it under both xsane and scanimage -b : $ scanimage -b Scanning -1 pages, incrementing by 1, numbering from 1 Scanning

[sane-devel] sane_cancel()

2008-07-16 Thread René Rebe
Hi, m. allan noah wrote: On 7/15/08, K?re S?rs kare.sars at kolumbus.fi wrote: Hi again, On Wednesdayen den 16 July 2008 02:02:36 K?re S?rs wrote: Hi, I'm a bit confused with the use of sane_cancel(). I noticed today that the pixma backend requires a sane_cancel after each

[sane-devel] getenv(SANE_USB_TIMEOUT)

2008-07-16 Thread Lev A. Melnikovsky
Dear allan, On Wed, 16 Jul 2008 at 4:46am, m. allan noah wrote: man there already is a mechanism for the backend to change the timeout: man sanei_usb_set_timeout. which takes precedence, the env var or the man backend? My intention was to only modify sanei_usb_init function. This would

[sane-devel] getenv(SANE_USB_TIMEOUT)

2008-07-16 Thread m. allan noah
On 7/16/08, Lev A. Melnikovsky leva at hotmail.com wrote: Dear allan, On Wed, 16 Jul 2008 at 4:46am, m. allan noah wrote: man there already is a mechanism for the backend to change the timeout: man sanei_usb_set_timeout. which takes precedence, the env var or the man backend? My

[sane-devel] getenv(SANE_USB_TIMEOUT)

2008-07-16 Thread Lev A. Melnikovsky
...nice to hear from you On Wed, 16 Jul 2008 at 3:08pm, Ren? Rebe wrote: RR The user should not be able to mess the timeouts from the environment. Actually the user is always able to do _anything_ from the environment(LD_PRELOAD). And we do already have SANE_SCSICMD_TIMEOUT and

[sane-devel] problems with genesys and MD6228

2008-07-16 Thread Werner Holtfreter
Am Montag, 30. Juni 2008 06:53:34 schrieb stef: the only difference I could spot is slightly different motor acceleration tables. The ones generated by the backend are very close to the ones in windows logs, but in case your scanner's motor is less tolerant (or failing ?), it might not