[sane-standard] Button handling

[Étienne Bersac]

Hi

> you must be a front-end developer :)

You dare ! :P. Tanks for the explanation ;)

> > Is there an easy way to know if an option is for frontend itself or for
> > user ? For example, the plustek backend show 5 "button" option for my
> > CanoScan N1220U, and xsane shows an unsensitive checkbox for this
> > button, in a "buttons" frame. That's useless and even annoying for
> > end-users. Why is that option shown ? Is there a way for backend to
> > tell : this option is not for user. I think about SANE_CAP_HARD_SELECT.
> > Am i wrong ?
> 
> xsane does not handle reading button presses from backend AFAIK.

xsane just don't monitor button state. However, the "advanced settings"
dialog shows me a button (boolean, readonly).

Regards,
É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/20070122/6c09d47c/attachment.pgp