kopia lustrzana https://gitlab.com/sane-project/website
77 wiersze
3.0 KiB
HTML
77 wiersze
3.0 KiB
HTML
|
<!-- received="Tue Aug 17 10:51:44 1999 PDT" -->
|
|||
|
|
<!-- sent="Tue, 17 Aug 1999 18:52:54 +0100 (GMT)" -->
|
|||
|
|
<!-- name="Nick Lamb" -->
|
|||
|
|
<!-- email="njl98r@ecs.soton.ac.uk" -->
|
|||
|
|
<!-- subject="Re: SANE frames" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="37B996EC.DA375BF1@wolfsburg.de" -->
|
|||
|
|
<title>sane-devel: Re: SANE frames</title>
|
|||
|
|
<h1>Re: SANE frames</h1>
|
|||
|
|
<b>Nick Lamb</b> (<a href="mailto:njl98r@ecs.soton.ac.uk"><i>njl98r@ecs.soton.ac.uk</i></a>)<br>
|
|||
|
|
<i>Tue, 17 Aug 1999 18:52:54 +0100 (GMT)</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#215">[ date ]</a><a href="index.html#215">[ thread ]</a><a href="subject.html#215">[ subject ]</a><a href="author.html#215">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0216.html">Andreas Dilger: "Re: SANE frames"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0214.html">Oliver Rauch: "Re: SANE frames"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
On Tue, 17 Aug 1999, Oliver Rauch wrote:<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> I think we need to specify the code flow for multiple images that are</i><br>
|
|||
|
|
<i>> acquired with one scan and a code flow for multi page scan (adf).</i><br>
|
|||
|
|
<p>
|
|||
|
|
We could accomplish this with:<br>
|
|||
|
|
An additional "last_image" boolean, together with "last_frame" from the<br>
|
|||
|
|
existing standard. The last_frame would indicate the last frame of a<br>
|
|||
|
|
given image, and last_image would be set when this was also the last<br>
|
|||
|
|
frame of all for the whole page.<br>
|
|||
|
|
<p>
|
|||
|
|
Then the following code flow eats all the images on a single page. You<br>
|
|||
|
|
can repeat this process for any following pages.<br>
|
|||
|
|
<p>
|
|||
|
|
do {<br>
|
|||
|
|
do {<br>
|
|||
|
|
<br>
|
|||
|
|
sane_start(...) the new frame<br>
|
|||
|
|
sane_get_parameters(...) for last_frame, last_image etc.<br>
|
|||
|
|
/* Read the whole FRAME */<br>
|
|||
|
|
<br>
|
|||
|
|
} while (!last_frame);<br>
|
|||
|
|
} while (!last_image);<br>
|
|||
|
|
<p>
|
|||
|
|
For a simple desktop scanner, you'll never go around the outer loop more<br>
|
|||
|
|
than once, because they only support one image for one page, AFAIK<br>
|
|||
|
|
Most modern scanners never go around the inner loop more than once<br>
|
|||
|
|
either, because they don't do multi-pass scans.<br>
|
|||
|
|
<p>
|
|||
|
|
This doesn't hurt compatability too badly I hope, and it means you can<br>
|
|||
|
|
have any combination of multiple pages, images-per-page and frames<br>
|
|||
|
|
per image.<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> I hope the exisiting backends are able to handle this!</i><br>
|
|||
|
|
<p>
|
|||
|
|
Wouldn't be the first time we've had to fix a few backends, but I<br>
|
|||
|
|
doubt most scanners support ADF or multi-image scans anyway :)<br>
|
|||
|
|
<p>
|
|||
|
|
Nick.<br>
|
|||
|
|
<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="0216.html">Andreas Dilger: "Re: SANE frames"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0214.html">Oliver Rauch: "Re: SANE frames"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|