kopia lustrzana https://gitlab.com/sane-project/website
81 wiersze
4.1 KiB
HTML
81 wiersze
4.1 KiB
HTML
<!-- received="Sat Jun 6 05:42:36 1998 PDT" -->
|
|
<!-- sent="Sat, 6 Jun 1998 13:29:07 +0200 (MET DST)" -->
|
|
<!-- name="becka@rz.uni-duesseldorf.de" -->
|
|
<!-- email="becka@rz.uni-duesseldorf.de" -->
|
|
<!-- subject="Re: SANE options" -->
|
|
<!-- id="m0yiH9n-0000XoC@charon.beck-sw.de" -->
|
|
<!-- inreplyto="199806060520.WAA19457@panda.mostang.com" -->
|
|
<title>sane-devel: Re: SANE options</title>
|
|
<h1>Re: SANE options</h1>
|
|
<a href="mailto:becka@rz.uni-duesseldorf.de"><i>becka@rz.uni-duesseldorf.de</i></a><br>
|
|
<i>Sat, 6 Jun 1998 13:29:07 +0200 (MET DST)</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#47">[ date ]</a><a href="index.html#47">[ thread ]</a><a href="subject.html#47">[ subject ]</a><a href="author.html#47">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0048.html">Kevin Turner: "Re: HP psc/380"</a>
|
|
<li> <b>Previous message:</b> <a href="0046.html">Hugo van der Kooij: "Re: HP psc/380"</a>
|
|
<li> <b>In reply to:</b> <a href="0045.html">David Mosberger-Tang: "Re: SANE options"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0052.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
|
|
<li> <b>Reply:</b> <a href="0052.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
<i>> Peter> David, A quick SANE question... Is there any way to force an</i><br>
|
|
<i>> Peter> option reload after finishing a read operation?</i><br>
|
|
<i>> No, reads are assumed to be "side-effect" free (as far as the options</i><br>
|
|
<i>> are concerned).</i><br>
|
|
<p>
|
|
Hmm - as reads are normally "expensive" operations, too (compared to<br>
|
|
an option setting), we might simply want to re-read all options after<br>
|
|
a read ...<br>
|
|
<p>
|
|
<i>> Peter> Oh yes, another one, though I suspect I know the answer to</i><br>
|
|
<i>> Peter> this one. Is there any way for a backend to put up it's own</i><br>
|
|
<i>> Peter> dialog boxes for warnings or confirmations?</i><br>
|
|
<i>> </i><br>
|
|
<i>> Nope, not at this point. Printing messages wouldn't be hard to do,</i><br>
|
|
<i>> but dialog boxes are a bit trickier because sometimes there is no user</i><br>
|
|
<i>> to dialog with. What exactly did you have in mind?</i><br>
|
|
<p>
|
|
Yes. For scripting applications, there should not be "unpredictable"<br>
|
|
questions popping up. I got very upset at several windows programs<br>
|
|
doing that, when I tried to make macro-recorder scxripts for them <br>
|
|
for a few common tasks one of my customers has to do ...<br>
|
|
<p>
|
|
<i>> As a general comment, I fully expect that we'll have to make some</i><br>
|
|
<i>> adjustments to the SANE API to better support digital cameras. I'd</i><br>
|
|
<i>> suggest that, for now, you hack around problems you encounter as your</i><br>
|
|
<i>> progresses. Then, once we're confident we understand what's needed to</i><br>
|
|
<i>> support cameras well, we can then add the missing stuff to the API.</i><br>
|
|
<i>> Sounds reasonable?</i><br>
|
|
<p>
|
|
Yes ... there is already that "transparent data returned" change pending,<br>
|
|
and we should check further on what implications such backends may bring<br>
|
|
and then bring out SANE API 1.1 or something.<br>
|
|
<p>
|
|
CU,ANdy<br>
|
|
<p>
|
|
<pre>
|
|
--
|
|
= Andreas Beck | Email : <<a href="mailto:andreas.beck@ggi-project.org">andreas.beck@ggi-project.org</a>> =
|
|
<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="0048.html">Kevin Turner: "Re: HP psc/380"</a>
|
|
<li> <b>Previous message:</b> <a href="0046.html">Hugo van der Kooij: "Re: HP psc/380"</a>
|
|
<li> <b>In reply to:</b> <a href="0045.html">David Mosberger-Tang: "Re: SANE options"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0052.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
|
|
<li> <b>Reply:</b> <a href="0052.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|