[sane-standard] Button handling (was: SANE2 proposal: split button/option)

[Étienne Bersac]

Hi,

> The backend should have a table storing which button is for which
> action. This is doable. Some buttons do not have label (e.g. Canon
> CanoScan N1220U), then just use "button" label. For other case, that
> just suck to let the user attach random action to random button. Also,
> if frontend can be aware of button use, it can provide useful default
> action to a button.

Another proposal is to use "button-<action>" options of type
SANE_TYPE_BUTTON to handle one button. The SANE well-known option ref
doc document available <action>s and we discuss here to add other
actions as needed.

We might start with the following list :

      * scan
      * mail

Other should come as they are known. This is still the same issue : the
well-known-option documentation must be very active while SANE standard
itself shoul be very frozen :).

Please comments,
Étienne.
-- 
Verso l'Alto !
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message
	=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Url : http://lists.alioth.debian.org/pipermail/sane-standard/attachments/20070121/a8065d40/attachment.pgp