kopia lustrzana https://gitlab.com/sane-project/website
101 wiersze
4.6 KiB
HTML
101 wiersze
4.6 KiB
HTML
<!-- received="Mon Jan 4 10:50:27 1999 PST" -->
|
||
<!-- sent="Mon, 04 Jan 1999 13:49:21 -0500" -->
|
||
<!-- name="Andre Couture" -->
|
||
<!-- email="acouture@videotron.ca" -->
|
||
<!-- subject="Re: TWAIN - SANE interface : announce" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="TWAIN - SANE interface : announce" -->
|
||
<title>sane-devel: Re: TWAIN - SANE interface : announce</title>
|
||
<h1>Re: TWAIN - SANE interface : announce</h1>
|
||
<b>Andre Couture</b> (<a href="mailto:acouture@videotron.ca"><i>acouture@videotron.ca</i></a>)<br>
|
||
<i>Mon, 04 Jan 1999 13:49:21 -0500</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#52">[ date ]</a><a href="index.html#52">[ thread ]</a><a href="subject.html#52">[ subject ]</a><a href="author.html#52">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0053.html">Rodrigo Amaro: "Genius ColorPage-Vivid Pro II"</a>
|
||
<li> <b>Previous message:</b> <a href="0051.html">Nick Lamb: "Re: TWAIN - SANE interface : announce"</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0046.html">Arun Tanksali: "TWAIN - SANE interface : announce"</a>
|
||
<!-- nextthread="start" -->
|
||
<li> <b>Next in thread:</b> <a href="0063.html">Brian Macy: "Re: TWAIN - SANE interface : announce"</a>
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
Good point,<br>
|
||
I do know that the artec backend still not full proof, I've been working with<br>
|
||
Chris to fix problems.<br>
|
||
But as a fact, some frontend like scanner.cgi, and TWAIN also, do not seem to<br>
|
||
fully verify the availability of options before seting them.<br>
|
||
<p>
|
||
TWAIN looks good, and I know it's the first version and there will be many more.<br>
|
||
<p>
|
||
one problem I notice with most frontend, is that they are developped and tested<br>
|
||
for one backend and the authors has to rely on fixes from other tester, but<br>
|
||
unfortunatly and often fixes/changes seem to be lost or not implemented.<br>
|
||
<p>
|
||
Note that I'm not complaining, just making remarks in hope that developpers<br>
|
||
listen and help getting all of those projects standardized.<br>
|
||
<p>
|
||
Unfortunatly as of wednesday I won't be much help here since I'm moving to Europe<br>
|
||
for few months, but I'm sure when I'll be back that everything will be working<br>
|
||
like a charm ;-)<br>
|
||
<p>
|
||
/ac<br>
|
||
<p>
|
||
Nick Lamb wrote:<br>
|
||
<p>
|
||
<i>> On Mon, 4 Jan 1999, Andre Couture wrote:</i><br>
|
||
<i>></i><br>
|
||
<i>> > Hi there,</i><br>
|
||
<i>> ></i><br>
|
||
<i>> > I got it, but having problmes with the artec backend.</i><br>
|
||
<i>> ></i><br>
|
||
<i>> > It seem that the BRIGHTNESS and some other options are not always supported</i><br>
|
||
<i>> > by some backends.</i><br>
|
||
<i>> > I think that, if the options are left to '0' you should not try to set them.</i><br>
|
||
<i>> > I've experimented with "bypassing" the BRIGHTNESS from the backend and works</i><br>
|
||
<i>> > better.</i><br>
|
||
<i>> > But that sould be changed from the "frontend" which in this case is TWAIN.</i><br>
|
||
<i>></i><br>
|
||
<i>> If the artec backend reports an option "BRIGHTNESS", but when you set it,</i><br>
|
||
<i>> falls over or does something stupid, then it is broken. If the TWAIN</i><br>
|
||
<i>> frontend, which I've yet to test, puts lots of options up regardless of</i><br>
|
||
<i>> whether they are offered by the backend, then it is broken. However, the</i><br>
|
||
<i>> SANE specification doesn't say "If you receive weird option specifiers,</i><br>
|
||
<i>> please crash and burn", so the backend should handle it gracefully anyway.</i><br>
|
||
<i>></i><br>
|
||
<i>> I'm not sure which is the case here, but it sounds like (again) backends</i><br>
|
||
<i>> aren't sticking to SANE. Does someone else know?</i><br>
|
||
<i>></i><br>
|
||
<i>> Nick.</i><br>
|
||
<p>
|
||
<pre>
|
||
--
|
||
<p>
|
||
------------------------------------------------------------------------
|
||
Andre Couture
|
||
938934 Ontario Inc.
|
||
<a href="mailto:acouture@videotron.ca">mailto:acouture@videotron.ca</a>
|
||
<p>
|
||
<a href="mailto:search_n_find@yahoo.com">mailto:search_n_find@yahoo.com</a>
|
||
<p>
|
||
<p>
|
||
<p>
|
||
<p>
|
||
<pre>
|
||
--
|
||
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
||
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
||
</pre>
|
||
<!-- body="end" -->
|
||
<p>
|
||
<ul>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0053.html">Rodrigo Amaro: "Genius ColorPage-Vivid Pro II"</a>
|
||
<li> <b>Previous message:</b> <a href="0051.html">Nick Lamb: "Re: TWAIN - SANE interface : announce"</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0046.html">Arun Tanksali: "TWAIN - SANE interface : announce"</a>
|
||
<!-- nextthread="start" -->
|
||
<li> <b>Next in thread:</b> <a href="0063.html">Brian Macy: "Re: TWAIN - SANE interface : announce"</a>
|
||
<!-- reply="end" -->
|
||
</ul>
|