sane-project-website/old-archive/1998-06/0065.html

81 wiersze
3.7 KiB
HTML

<!-- received="Sun Jun 7 19:07:19 1998 PDT" -->
<!-- sent="Sun, 7 Jun 1998 04:30:29 +0200 (MET DST)" -->
<!-- name="becka@rz.uni-duesseldorf.de" -->
<!-- email="becka@rz.uni-duesseldorf.de" -->
<!-- subject="Re: SANE options" -->
<!-- id="m0yiVE5-0000ZpC@charon.beck-sw.de" -->
<!-- inreplyto="19980606202217Z13342-2383+128@scapa.cs.ualberta.ca" -->
<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>Sun, 7 Jun 1998 04:30:29 +0200 (MET DST)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#65">[ date ]</a><a href="index.html#65">[ thread ]</a><a href="subject.html#65">[ subject ]</a><a href="author.html#65">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0066.html">Oliver.Rauch@Wolfsburg.DE: "Re: Problems with CANCEL"</a>
<li> <b>Previous message:</b> <a href="0064.html">Chip Atkinson: "Mustek questions"</a>
<li> <b>In reply to:</b> <a href="0052.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0071.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
<li> <b>Reply:</b> <a href="0071.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hi !<br>
<p>
<i>&gt; &gt; &gt; Nope, not at this point. Printing messages wouldn't be hard to do,</i><br>
<i>&gt; &gt; &gt; but dialog boxes are a bit trickier because sometimes there is no user</i><br>
<i>&gt; &gt; &gt; to dialog with. What exactly did you have in mind?</i><br>
<i>&gt; </i><br>
<i>&gt; It might be useful if there were a way for the backend to say to the</i><br>
<i>&gt; frontend "I have a status message", </i><br>
<p>
This is easy. SANE supports text fields, and those can be set from the<br>
backend easily be requesting a full option reload.<br>
<p>
<i>&gt; or "I have a yes/no/cancel question", </i><br>
<p>
Please if at all possible - avoid that. This is really bad for <br>
scripting ...<br>
<p>
<i>&gt; aren't quite enough, because the backend might want to ask a question</i><br>
<i>&gt; in the middle of an API function call, and then the call has to exit</i><br>
<i>&gt; and somehow be restarted with the information it didn't have. So what</i><br>
<i>&gt; about frontends supplying callback functions to the backend at</i><br>
<i>&gt; initialization time? For example, a callback that answers a</i><br>
<i>&gt; yes/no/cancel question might have prototype</i><br>
<p>
This complicates quite a bunch of things. It is _really_ needed ?<br>
Could you give an example ?<br>
<p>
<i>&gt; Obviously either approach involves an API change so it would have to</i><br>
<i>&gt; be for a future version. </i><br>
<p>
Regarding returning status messages, this can easily be solved without <br>
changing API. <br>
<p>
CU,Andy<br>
<p>
<pre>
--
= Andreas Beck | Email : &lt;<a href="mailto:andreas.beck@ggi-project.org">andreas.beck@ggi-project.org</a>&gt; =
<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="0066.html">Oliver.Rauch@Wolfsburg.DE: "Re: Problems with CANCEL"</a>
<li> <b>Previous message:</b> <a href="0064.html">Chip Atkinson: "Mustek questions"</a>
<li> <b>In reply to:</b> <a href="0052.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0071.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
<li> <b>Reply:</b> <a href="0071.html">charter@cs.ualberta.ca: "Re: SANE options"</a>
<!-- reply="end" -->
</ul>