Le Friday 14 March 2008 15:31:08, vous avez ?crit?:
> Hi,
>
> That's very nice to have button handling in your backend. Please provide
> semantic button naming like "paper-in", "trigger", "cancel" or default
> to "auto" or something similar. Also, please use boolean rather than 0/1
> int option for button, this is as well more semantic. Button naming can
> be done per model, without modifying the underlying option handling
> (based on button number).
They are allready of 'type' boolean:
scanner->opt[i].type = SANE_TYPE_BOOL;
I may put a more accurate 'title' and 'desc' field (it was on my TODO
list).
For the 'name' field, I'll stick to "button%d" like it is currently done in
others backends.
>
> I'm telling you this, writing hal-scanner support which should help a
> lot on makeing use of scanner buttons in frontend like GNOME Scan and
> KDE. The idea is to help as much as possible the frontend to auto
> determine what to do on button event.
>
> I would like to open a discussion about button naming for 1.2, once i
> have a reasonnable hald-addon-scanner version.
>
> Regards,
> ?tienne.
Having 'well known' button names seems sensible. Have you allready got
an
idea ? For instance the 4470c has:
- power button
- scanner button
- www button
- copy button
- mail button
- printer button
- '+' button
- '-' button
- toggle color/gray scan mode button
- spanner button
- red triangle within a red circle button
Regards,
Stef
