[sane-devel] plustek:libusb bugs on canon canoscan n1220U
bersace03 at laposte.net
Wed Aug 9 13:20:28 UTC 2006
> SANE standard 1 does not specify how to handle scanner buttons,
> but it is clear, that an option, which deals with a button has to deliver
> a value (button pressed or not). Regarding that requirement, you have either
> to use SANE_TYPE_BOOL or SANE_TYPE_INT - I choose BOOL.
> SANE_TYPE_BUTTON is maybe misleading. It is intended to be used by a backend
> to allow changes by pressing that button from the GUI and NOT to reflect
> the status of a scanner button. An option of type SANE_TYPE_BUTTON has no value.
> See also chapter 18.104.22.168 of the SANE Standard
Okey, the strange part of this button handling is : how an app using
sane know an option reflect a button status ? Just in order to ignore
that option. For example, xsane advanced options dialog shows a fieldset
entitled "Buttons" with one option "Scanner button" which is inactive
and always false. That's useless. I don't know how multiple buttons are
handle. Do the app has to parse name or title or desc field in order to
find a "button" string and then treat the option as a button state
Thanks for all.
Verso l'Alto !
More information about the sane-devel