kopia lustrzana https://gitlab.com/sane-project/website
65 wiersze
2.9 KiB
HTML
65 wiersze
2.9 KiB
HTML
<!-- received="Tue Aug 17 09:18:48 1999 PDT" -->
|
|
<!-- sent="Tue, 17 Aug 1999 09:18:46 -0700" -->
|
|
<!-- name="David Mosberger-Tang" -->
|
|
<!-- email="David.Mosberger@acm.org" -->
|
|
<!-- subject="Re: SANE frames" -->
|
|
<!-- id="199908171618.JAA01279@panda.mostang.com" -->
|
|
<!-- inreplyto="37B71520.F0BD8617@martoneconsulting.com" -->
|
|
<title>sane-devel: Re: SANE frames</title>
|
|
<h1>Re: SANE frames</h1>
|
|
<b>David Mosberger-Tang</b> (<a href="mailto:David.Mosberger@acm.org"><i>David.Mosberger@acm.org</i></a>)<br>
|
|
<i>Tue, 17 Aug 1999 09:18:46 -0700</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#211">[ date ]</a><a href="index.html#211">[ thread ]</a><a href="subject.html#211">[ subject ]</a><a href="author.html#211">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0212.html">David Mosberger-Tang: "Re: SANE frames"</a>
|
|
<li> <b>Previous message:</b> <a href="0210.html">Oliver Rauch: "Re: SANE frames"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
<i>>>>>> On Mon, 16 Aug 1999 17:42:47 +0200, Oliver Rauch <<a href="mailto:oliver.rauch@Wolfsburg.DE">oliver.rauch@Wolfsburg.DE</a>> said:</i><br>
|
|
<p>
|
|
Oliver> the sane standard defines of how much frames an image<br>
|
|
Oliver> consists. After the last frame - that means if the image is<br>
|
|
Oliver> transferred completly - the frontend has to call<br>
|
|
Oliver> sane_cancel.<br>
|
|
<p>
|
|
Actually, IIRC, our intent was indeed to allow the call sequence that<br>
|
|
Tom describes. Note that in 4.4 it says:<br>
|
|
<p>
|
|
"If the frontend expects additional frames (e.g., the individual channels <br>
|
|
in of a red/green/blue image or multiple images), it can call sane_start()<br>
|
|
^^^^^^^^^^^^^^^^^^<br>
|
|
again."<br>
|
|
<p>
|
|
Also, note that xcam does acquire multiple images without calling<br>
|
|
sane_cancel(). (It's an amusing exercise to test a scanner with xcam,<br>
|
|
actually ;-)<br>
|
|
<p>
|
|
In other words, the idea is to have sane_start() be called, and<br>
|
|
collect as many images as the frontend wants (which could in turn<br>
|
|
consist of multiple frames each as indicated by frame-type) and when<br>
|
|
the frontend is done, it should call sane_cancel(). Sometimes it's<br>
|
|
better to think of sane_cancel() as "sane_stop()" but that name would<br>
|
|
have had some misleading connotations as well, that's why we stuck<br>
|
|
with "cancel".<br>
|
|
<p>
|
|
--david<br>
|
|
<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="0212.html">David Mosberger-Tang: "Re: SANE frames"</a>
|
|
<li> <b>Previous message:</b> <a href="0210.html">Oliver Rauch: "Re: SANE frames"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|