kopia lustrzana https://gitlab.com/sane-project/website
148 wiersze
6.9 KiB
HTML
148 wiersze
6.9 KiB
HTML
<!-- received="Mon Jul 26 10:59:24 1999 PDT" -->
|
||
<!-- sent="Mon, 26 Jul 1999 20:12:45 +0200" -->
|
||
<!-- name="Oliver Rauch" -->
|
||
<!-- email="oliver.rauch@Wolfsburg.DE" -->
|
||
<!-- subject="Re: Anyone with a Umax Document Feeder?" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="Anyone with a Umax Document Feeder?" -->
|
||
<title>sane-devel: Re: Anyone with a Umax Document Feeder?</title>
|
||
<h1>Re: Anyone with a Umax Document Feeder?</h1>
|
||
<b>Oliver Rauch</b> (<a href="mailto:oliver.rauch@Wolfsburg.DE"><i>oliver.rauch@Wolfsburg.DE</i></a>)<br>
|
||
<i>Mon, 26 Jul 1999 20:12:45 +0200</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#177">[ date ]</a><a href="index.html#177">[ thread ]</a><a href="subject.html#177">[ subject ]</a><a href="author.html#177">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0178.html">Chris Pinkham: "Re: Anyone with a Umax Document Feeder?"</a>
|
||
<li> <b>Previous message:</b> <a href="0176.html">Andreas: "Re: CVS web page?"</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0152.html">Oliver Rauch: "Anyone with a Umax Document Feeder?"</a>
|
||
<!-- nextthread="start" -->
|
||
<li> <b>Next in thread:</b> <a href="0179.html">Oliver Rauch: "Re: Anyone with a Umax Document Feeder?"</a>
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
Nick Lamb wrote:<br>
|
||
<p>
|
||
<i>> On Sun, 25 Jul 1999, Oliver Rauch wrote:</i><br>
|
||
<i>></i><br>
|
||
<i>> > I am in contact with David to add some things to the sane api.</i><br>
|
||
<i>> > One of this is to define how to handle a document feeder.</i><br>
|
||
<i>> > The idea is very simple:</i><br>
|
||
<i>> > We define a well known option "mode" that defines the scanmode</i><br>
|
||
<i>> > such as "Flatbed", "Transparency Adapter" or "Automatic Document Feeder".</i><br>
|
||
<i>></i><br>
|
||
<i>> I wonder if this is short-sighted? Can you explain what it's for?</i><br>
|
||
<i>> Regardless it should probably be called something other than "mode".</i><br>
|
||
<p>
|
||
It is called mode because it already is used this way by most backends,<br>
|
||
it is defined in saneopts as SANE_NAME_SCAN_MODE "mode"<br>
|
||
<p>
|
||
abaton.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
agfafocus.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
apple.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
artec.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
canon.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
coolscan.c: scanner->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
epson.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
microtek2.c: sod[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
microtek.c: sod[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
mustek.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
pint.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
ricoh.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
sharp.c: s->opt[XOPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
snapscan.c: po[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
tamarack.c: s->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
umax.c: scanner->opt[OPT_MODE].name = SANE_NAME_SCAN_MODE;<br>
|
||
<p>
|
||
<p>
|
||
<i>> > If the option "mode" is set to "Automatic Document Feeder" xsane scans</i><br>
|
||
<i>> > until it gets an error</i><br>
|
||
<i>> > (such as out of paper).</i><br>
|
||
<i>></i><br>
|
||
<i>> What will this SANE option "mode" actually do? I don't mean in Xsane</i><br>
|
||
<i>> (which is a frontend, and therefore doesn't HAVE any SANE options) I</i><br>
|
||
<i>> want to know what it does in the backend.</i><br>
|
||
<i>></i><br>
|
||
<p>
|
||
option mode is a string list with texts like "Flatbed", "Transparancy Adapter"<br>
|
||
or "Automatic Document Feeder". If the user selects<br>
|
||
"Automatic Document Feeder" the scanner activates the ADF.<br>
|
||
For most scanners this means that the scanhead is not moved at all if<br>
|
||
you start a scan. Instead the paper is moved over the fixed scanhead.<br>
|
||
<p>
|
||
<p>
|
||
<i>></i><br>
|
||
<i>> > Functions such as unload page or load new page can be realised by a button</i><br>
|
||
<i>> > that calls a function of the backend, there is nothing that must be defined</i><br>
|
||
<i>> > for it!</i><br>
|
||
<i>></i><br>
|
||
<i>> Like this?</i><br>
|
||
<i>> SANE_TYPE_BUTTON "unload page"</i><br>
|
||
<i>> SANE_TYPE_BUTTON "next page"</i><br>
|
||
<i>> There are existing buttons like this in the HP backend, I just want the</i><br>
|
||
<i>> SANE documentation altered to make them "Well Known Options" and define</i><br>
|
||
<i>> the exact behaviour in a central place.</i><br>
|
||
<i>></i><br>
|
||
<i>> It makes sense for XSane to use these buttons internally, while also</i><br>
|
||
<i>> presenting them in the user-interface. You can programatically "push"</i><br>
|
||
<i>> the button for each new page. In non-ADF-aware SANE apps, like the</i><br>
|
||
<i>> current XSane, the buttons still work.</i><br>
|
||
<i>></i><br>
|
||
<p>
|
||
This does not work as a common ADF support because most scanners do not<br>
|
||
have the ability to load/unload the paper.<br>
|
||
<p>
|
||
If the option mode is set to ADF, the backend automatically has to load<br>
|
||
a new paper at the beginning of the scan.<br>
|
||
<p>
|
||
I see that this is not so simple as I thought, so I will have to add an<br>
|
||
explanation<br>
|
||
of this to the sane doc.<br>
|
||
<p>
|
||
We could make the load/unload options well known, but I don`t think that<br>
|
||
this will mean much. A frontend will not be able to use this with much sense.<br>
|
||
<p>
|
||
So I suggest to add an ADF mode that automatically loads/unloads the paper<br>
|
||
and this should be started when the option "mode" is set to ADF.<br>
|
||
<p>
|
||
<i>></i><br>
|
||
<i>> > The probelm is that the hp backend is not compatible to this.</i><br>
|
||
<i>> > The umax backend does work this way so I would prefer a UMAX document feeder.</i><br>
|
||
<i>></i><br>
|
||
<i>> How does the UMAX backend work?</i><br>
|
||
<i>></i><br>
|
||
<p>
|
||
See above.<br>
|
||
It is not the umax backend that loads/unloads the paper.<br>
|
||
It simply tells the scanner to activate ADF mode and the scanner itself<br>
|
||
does the rest. There are no functions to load/unload the paper.<br>
|
||
<p>
|
||
Bye<br>
|
||
<p>
|
||
Oliver<br>
|
||
<p>
|
||
<pre>
|
||
--
|
||
EMAIL: <a href="mailto:Oliver.Rauch@Wolfsburg.DE">Oliver.Rauch@Wolfsburg.DE</a>
|
||
WWW: <a href="http://www.wolfsburg.de/~rauch">http://www.wolfsburg.de/~rauch</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="0178.html">Chris Pinkham: "Re: Anyone with a Umax Document Feeder?"</a>
|
||
<li> <b>Previous message:</b> <a href="0176.html">Andreas: "Re: CVS web page?"</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0152.html">Oliver Rauch: "Anyone with a Umax Document Feeder?"</a>
|
||
<!-- nextthread="start" -->
|
||
<li> <b>Next in thread:</b> <a href="0179.html">Oliver Rauch: "Re: Anyone with a Umax Document Feeder?"</a>
|
||
<!-- reply="end" -->
|
||
</ul>
|