sane-project-website/old-archive/1997-09/0027.html

38 wiersze
1.4 KiB
HTML

<!-- received="Tue Sep 30 13:10:06 1997 MST" -->
<!-- sent="Tue, 30 Sep 1997 13:18:17 -0700" -->
<!-- name="Matto Marjanovic" -->
<!-- email="maddog@mir.com" -->
<!-- subject="semantics of SANE_CAP_ADVANCED?" -->
<!-- id="199709302009.QAA06314@yoo-hoo.ai.mit.edu" -->
<!-- inreplyto="" -->
<title>sane-devel: semantics of SANE_CAP_ADVANCED?</title>
<h1>semantics of SANE_CAP_ADVANCED?</h1>
<b>Matto Marjanovic</b> (<a href="mailto:maddog@mir.com"><i>maddog@mir.com</i></a>)<br>
<i>Tue, 30 Sep 1997 13:18:17 -0700</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#27">[ date ]</a><a href="index.html#27">[ thread ]</a><a href="subject.html#27">[ subject ]</a><a href="author.html#27">[ author ]</a>
<!-- next="start" -->
<li> <b>Previous message:</b> <a href="0026.html">Rogier Wolff: "Re: success: Mustek 1200SP, firmware 1.02"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
For device options (in a backend), where and how should the SANE_CAP_ADVANCED<br>
capability flag be used?<br>
<p>
Should it be set for individual options, or should it only be applied to<br>
option groups? The documentation seems to imply the former, but the usage<br>
I see in some backends implies the latter.<br>
<p>
<p>
-matt m.<br>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Previous message:</b> <a href="0026.html">Rogier Wolff: "Re: success: Mustek 1200SP, firmware 1.02"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>