szukw000 at arcor.de writes: > xsane needs SANE_CAP_ALWAYS_SETTABLE in : xsane-0.996/src/xsane-back-gtk.c
> --- include/sane/sane.h.orig 2009-03-01 20:41:13.000000000 +0100 > +++ include/sane/sane.h 2009-03-01 20:41:41.000000000 +0100 > @@ -112,6 +112,7 @@ > #define SANE_CAP_AUTOMATIC (1 << 4) > #define SANE_CAP_INACTIVE (1 << 5) > #define SANE_CAP_ADVANCED (1 << 6) > +#define SANE_CAP_ALWAYS_SETTABLE (1 << 7) > > #define SANE_OPTION_IS_ACTIVE(cap) (((cap) & SANE_CAP_INACTIVE) == 0) > #define SANE_OPTION_IS_SETTABLE(cap) (((cap) & SANE_CAP_SOFT_SELECT) != 0) Please note that SANE_CAP_ALWAYS_SETTABLE is _not_ part of the current stable API[1]. Please also note that the draft specification for SANE2[2] mentions the following with respect to capability flags: SANE_CAP_HIDDEN 128 SANE_CAP_ALWAYS_SETTABLE 256 Adding it with a value of (1 << 7) == 128 is probably a Bad Thing. [1] http://sane.alioth.debian.org/html/doc011.html#s4.2.9.7 [2] http://sane.alioth.debian.org/sane2/0.08/doc011.html#s4.2.9.7 Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
