TWAIN looks good, and I know it's the first version and there will be many more.
one problem I notice with most frontend, is that they are developped and tested
for one backend and the authors has to rely on fixes from other tester, but
unfortunatly and often fixes/changes seem to be lost or not implemented.
Note that I'm not complaining, just making remarks in hope that developpers
listen and help getting all of those projects standardized.
Unfortunatly as of wednesday I won't be much help here since I'm moving to Europe
for few months, but I'm sure when I'll be back that everything will be working
like a charm ;-)
/ac
Nick Lamb wrote:
> On Mon, 4 Jan 1999, Andre Couture wrote:
>
> > Hi there,
> >
> > I got it, but having problmes with the artec backend.
> >
> > It seem that the BRIGHTNESS and some other options are not always supported
> > by some backends.
> > I think that, if the options are left to '0' you should not try to set them.
> > I've experimented with "bypassing" the BRIGHTNESS from the backend and works
> > better.
> > But that sould be changed from the "frontend" which in this case is TWAIN.
>
> If the artec backend reports an option "BRIGHTNESS", but when you set it,
> falls over or does something stupid, then it is broken. If the TWAIN
> frontend, which I've yet to test, puts lots of options up regardless of
> whether they are offered by the backend, then it is broken. However, the
> SANE specification doesn't say "If you receive weird option specifiers,
> please crash and burn", so the backend should handle it gracefully anyway.
>
> I'm not sure which is the case here, but it sounds like (again) backends
> aren't sticking to SANE. Does someone else know?
>
> Nick.
-------------------------------------------------------------------------- Andre Couture 938934 Ontario Inc. mailto:acouture@videotron.ca
mailto:search_n_find@yahoo.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com