# Re: May sane_init fail?

Ingo Wilken (Ingo.Wilken@Informatik.Uni-Oldenburg.DE)
Wed, 28 Apr 1999 19:10:33 +0200 (MET DST)

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Peter Kirchgessner: "Re: How to config my HP Scanjet 4p to work with SANE ?"
- Previous message: abel deuring: "Re: HP PhotoSmart R030 vs. SANE 1.01"
- In reply to: Petter Reinholdtsen: "Re: May sane_init fail?"

> Anyway. I'm now writing a patch to sane 1.0.1 with my suggested
> change. I suggest three valid responses from sane_init():
> SANE_STATUS_GOOD - Success
> SANE_STATUS_NO_MEM - Ran out of memory
> SANE_STATUS_UNSUPPORTED - Not supported on this machines current
> configuration
> Would there be need for more return values?

What's the suggested return values for a backend/SANE version mismatch?
I'm currently using SANE_STATUS_UNSUPPORTED (seems logical), but
SANE_STATUS_INVAL could be used too.

BTW, it seems that almost no backend checks the version number, and most
backends distributed with 1.0.x are listed as version 0.something in the
"supported scanners" webpage - not good.

Regards,
Ingo

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

- Next message: Peter Kirchgessner: "Re: How to config my HP Scanjet 4p to work with SANE ?"
- Previous message: abel deuring: "Re: HP PhotoSmart R030 vs. SANE 1.01"
- In reply to: Petter Reinholdtsen: "Re: May sane_init fail?"