sane-project-website/old-archive/1999-08/0187.html

65 wiersze
2.9 KiB
HTML

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

<!-- received="Sun Aug 15 18:31:57 1999 PDT" -->
<!-- sent="Sun, 15 Aug 1999 20:49:56 -0400" -->
<!-- name="Tom Martone" -->
<!-- email="tom@martoneconsulting.com" -->
<!-- subject="Re: SANE V2" -->
<!-- id="" -->
<!-- inreplyto="SANE V2" -->
<title>sane-devel: Re: SANE V2</title>
<h1>Re: SANE V2</h1>
<b>Tom Martone</b> (<a href="mailto:tom@martoneconsulting.com"><i>tom@martoneconsulting.com</i></a>)<br>
<i>Sun, 15 Aug 1999 20:49:56 -0400</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#187">[ date ]</a><a href="index.html#187">[ thread ]</a><a href="subject.html#187">[ subject ]</a><a href="author.html#187">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0188.html">Andreas Beck: "Re: SANE V2"</a>
<li> <b>Previous message:</b> <a href="0186.html">Nick Lamb: "Re: SANE V2"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Nick Lamb wrote:<br>
<i>&gt; </i><br>
<i>&gt; On Sun, 15 Aug 1999, Tom Martone wrote:</i><br>
<i>&gt; </i><br>
<i>&gt; &gt; Another use of the text frame might be to allow the backend to</i><br>
<i>&gt; &gt; report its configuration. Wouldn't it be nice if the backend information</i><br>
<i>&gt; &gt; shown in the Xsane dialog could include a little text area that simply</i><br>
<i>&gt; &gt; displayed a textual summary of the scanner's inquired</i><br>
<i>&gt; &gt; configuration and capabilities? This would be especially useful if</i><br>
<i>&gt; &gt; the scanner were being accessed through saned. I don't know the mechanism</i><br>
<i>&gt; &gt; by which the front end would ask for this, though.</i><br>
<i>&gt; </i><br>
<i>&gt; Hmm. I think what you're talking about here is stuff already better</i><br>
<i>&gt; handled in SANE Options. Have you looked at that stuff in SANE 1.0?</i><br>
<i>&gt; I think it's a very powerful way to express anything a user might want</i><br>
<i>&gt; to know, and more, about the scanner's current state of mind.</i><br>
<i>&gt; </i><br>
<i>&gt; Also, in SANE Options it's clear which stuff you can change, and which</i><br>
<i>&gt; stuff you can't -- there's even a way to say "The user can change this,</i><br>
<i>&gt; but only by {pressing a button, flipping a dipswitch, opening a panel}</i><br>
<i>&gt; on the scanner itself.</i><br>
<p>
I should have kept my mouth shut about that example; it's a poor one.<br>
<p>
You've made me think about some useful read-only options that I should<br>
add, though. Thanks.<br>
<p>
Tom Martone<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="0188.html">Andreas Beck: "Re: SANE V2"</a>
<li> <b>Previous message:</b> <a href="0186.html">Nick Lamb: "Re: SANE V2"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>