kopia lustrzana https://gitlab.com/sane-project/website
75 wiersze
3.6 KiB
HTML
75 wiersze
3.6 KiB
HTML
<!-- received="Fri Jun 5 22:20:13 1998 PDT" -->
|
|
<!-- sent="Fri, 5 Jun 1998 22:20:12 -0700" -->
|
|
<!-- name="David Mosberger-Tang" -->
|
|
<!-- email="David.Mosberger@acm.org" -->
|
|
<!-- subject="Re: SANE options" -->
|
|
<!-- id="199806060520.WAA19457@panda.mostang.com" -->
|
|
<!-- inreplyto="m0yhmV6-001reOC@lucent.com" -->
|
|
<title>sane-devel: Re: SANE options</title>
|
|
<h1>Re: SANE options</h1>
|
|
<b>David Mosberger-Tang</b> (<a href="mailto:David.Mosberger@acm.org"><i>David.Mosberger@acm.org</i></a>)<br>
|
|
<i>Fri, 5 Jun 1998 22:20:12 -0700</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#45">[ date ]</a><a href="index.html#45">[ thread ]</a><a href="subject.html#45">[ subject ]</a><a href="author.html#45">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0046.html">Hugo van der Kooij: "Re: HP psc/380"</a>
|
|
<li> <b>Previous message:</b> <a href="0044.html">David Mosberger-Tang: "Re: Scanner support"</a>
|
|
<li> <b>In reply to:</b> <a href="0036.html">Peter Fales: "SANE options"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0047.html">becka@rz.uni-duesseldorf.de: "Re: SANE options"</a>
|
|
<li> <b>Reply:</b> <a href="0047.html">becka@rz.uni-duesseldorf.de: "Re: SANE options"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
<i>>>>>> On Thu, 4 Jun 98 21:45 CDT, <a href="mailto:psfales@earthling.net">psfales@earthling.net</a> (Peter Fales) said:</i><br>
|
|
<p>
|
|
Peter> David, A quick SANE question... Is there any way to force an<br>
|
|
Peter> option reload after finishing a read operation?<br>
|
|
<p>
|
|
No, reads are assumed to be "side-effect" free (as far as the options<br>
|
|
are concerned).<br>
|
|
<p>
|
|
Peter> On my DC-25 backend, the allowable range of one of the<br>
|
|
Peter> options (the number of images stored in the camera) is<br>
|
|
Peter> modified by the the read, if the read involves taking a new<br>
|
|
Peter> picture. So, I would to be able to reload the options at<br>
|
|
Peter> that point.<br>
|
|
<p>
|
|
OK, got it.<br>
|
|
<p>
|
|
Peter> Oh yes, another one, though I suspect I know the answer to<br>
|
|
Peter> this one. Is there any way for a backend to put up it's own<br>
|
|
Peter> dialog boxes for warnings or confirmations?<br>
|
|
<p>
|
|
Nope, not at this point. Printing messages wouldn't be hard to do,<br>
|
|
but dialog boxes are a bit trickier because sometimes there is no user<br>
|
|
to dialog with. What exactly did you have in mind?<br>
|
|
<p>
|
|
As a general comment, I fully expect that we'll have to make some<br>
|
|
adjustments to the SANE API to better support digital cameras. I'd<br>
|
|
suggest that, for now, you hack around problems you encounter as your<br>
|
|
progresses. Then, once we're confident we understand what's needed to<br>
|
|
support cameras well, we can then add the missing stuff to the API.<br>
|
|
Sounds reasonable?<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="0046.html">Hugo van der Kooij: "Re: HP psc/380"</a>
|
|
<li> <b>Previous message:</b> <a href="0044.html">David Mosberger-Tang: "Re: Scanner support"</a>
|
|
<li> <b>In reply to:</b> <a href="0036.html">Peter Fales: "SANE options"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0047.html">becka@rz.uni-duesseldorf.de: "Re: SANE options"</a>
|
|
<li> <b>Reply:</b> <a href="0047.html">becka@rz.uni-duesseldorf.de: "Re: SANE options"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|