[sane-devel] sane_get_devices() questions

2009-06-01 Thread Kåre Särs
Hi, I have an unexpected behavior with sane_get_device(). In the standard (1.04) it states (4.3.3) This function can be called repeatedly to detect when new devices become available. From that I expected that this sequence would work: sane_init(version, 0); sane_get_device(device_list,

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-06-01 Thread Olaf Meeuwissen
m. allan noah kitno455 at gmail.com writes: [snip] I also would like to add a generic 'SANE_STATUS_RETRY' for those cases where the backend has to block during sane_start because it must ingest the entire image before the size is known. The standard allows backends to return an unknown

[sane-devel] sane_get_devices() questions

2009-06-01 Thread Olaf Meeuwissen
m. allan noah kitno455 at gmail.com writes: there was a bug in sanei_usb which prevented sane from discovering newly added scanners. This was fixed in 1.0.20. Unfortunately, some backends only ask the system for a list of scanners during sane_init(). I fixed mine, but I bet other backends are

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-06-01 Thread Olaf Meeuwissen
m. allan noah kitno455 at gmail.com writes: On Sun, May 31, 2009 at 7:23 PM, Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote: m. allan noah kitno455 at gmail.com writes: [snip] I also would like to add a generic 'SANE_STATUS_RETRY' for those cases where the backend has to block during

[sane-devel] Epson PX700W/Artisan 700 network scanning

2009-06-01 Thread Alessandro Zummo
On Wed, 27 May 2009 20:18:55 -0500 Chris Bagwell chris at cnpbagwell.com wrote: Yep, thats most likely what happened. The epson2 backend can detect Artisan 700 and 800's over the network just fine. There are some issues that cause it to lock printer up and require power cycle; based on

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-06-01 Thread stef
Le vendredi 29 mai 2009 22:23:23 m. allan noah, vous avez ?crit : well, lets re-open the discussion of the return codes. Julien had some reservations about this technique. I dont have a problem with it, as long as we formalize it in the standard exactly which status codes require retry. I also

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-06-01 Thread m. allan noah
On Mon, Jun 1, 2009 at 3:08 PM, stef stef.dev at free.fr wrote: Le vendredi 29 mai 2009 22:23:23 m. allan noah, vous avez ?crit : well, lets re-open the discussion of the return codes. Julien had some reservations about this technique. I dont have a problem with it, as long as we formalize it

[sane-devel] sane_get_devices() questions

2009-06-01 Thread Kåre Särs
On Monday 01 June 2009 00:58:41 m. allan noah wrote: there was a bug in sanei_usb which prevented sane from discovering newly added scanners. This was fixed in 1.0.20. Unfortunately, some backends only ask the system for a list of scanners during sane_init(). I fixed mine, but I bet other

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-06-01 Thread stef
Le lundi 1 juin 2009 21:14:05 m. allan noah, vous avez ?crit : On Mon, Jun 1, 2009 at 3:08 PM, stef stef.dev at free.fr wrote: ... I think a SANE_STATUS_UNCALIBRATED would also be useful. It would let a frontend that the scan can start, but will be uncalibrated. This would fit in

[sane-devel] sane_get_devices() questions

2009-06-01 Thread m. allan noah
2009/6/1 K?re S?rs kare.sars at iki.fi: On Monday 01 June 2009 00:58:41 m. allan noah wrote: there was a bug in sanei_usb which prevented sane from discovering newly added scanners. This was fixed in 1.0.20. Unfortunately, some backends only ask the system for a list of scanners during

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-06-01 Thread Alessandro Zummo
On Mon, 1 Jun 2009 15:14:05 -0400 m. allan noah kitno455 at gmail.com wrote: what will the front-end do with that info? just plow ahead and ignore it? Thats not really a status, but more of a param of the image data. I think if you want that info, it makes more sense to turn the last frame

[sane-devel] byteorder.h

2009-06-01 Thread Chris Bagwell
If no one else gives it a go, I'll have a hand at updating the autoconf macro. I've not much experience with cross platform locations of those defines. I see in my Fedora 11 Linux box that alot of those duplicates are defined in endian.h (although perhaps hidden by some #ifdef's) and the