[sane-devel] Well known sensor

Hi, > the windows software does boolean logic on this value, along with > the state of the other buttons and sensors, to provide many 'preset' > scan modes. it might be nice if your code could support that idea. Agree, i'll implement this once i have user feedback. I may ping you then for deeper

[sane-devel] Well known sensor

Hi, I read a bit the fujitsu backend source (sadly, i don't have such fuji scanners). The sensor handling is exactly what i asked for :D !! Each sensor is named "button-" and is not a number but something like "send", "scan", etc. :) That is PER - FECT :D I just suggest to expand this behaviour

[sane-devel] Well known sensor

Hi, > the button should be called something as close as possible to the > writing on the scanner, not the front-end authors list of words he > understands. I don't mean to impose naming, just propose convention. Is the goal of SANE just to dump device design or to abstract device ? I guess the la

[sane-devel] Well known sensor

Hi, KScannerButtons work like this. See http://jice.free.fr/KScannerButtons/ . However, this is completely incompatible with end user (think grand-ma) who just want the scanner to cancel once she pushed that damn cancel button, and not one more popup asking what to do (while the scanning is conti

[sane-devel] Well known sensor

"m. allan noah" wrote: > understands. there is no 'email' button on a fujitsu, there is a 'Send > to' button. This is of course complicated by the fact that some > scanners have localized versions and some only have pictures. UI nightmare :-) > then, you dont need to interpret the values, you o

[sane-devel] Well known sensor

On Mon, 17 Mar 2008 20:17:50 +0100 Julien BLACHE wrote: > The backend doesn't know, either. Currently the buttons are used > mostly by custom frontends which do know what's hiding behind the > buttons. > > There is no standard in SANE, which is a problem, but even worse > there's nothing standar

[sane-devel] Well known sensor

On 3/17/08, ?tienne Bersac wrote: > Hi, > > I read a bit the fujitsu backend source (sadly, i don't have such fuji > scanners). The sensor handling is exactly what i asked for :D !! > > Each sensor is named "button-" and is not a number but > something like "send", "scan", etc. :) That is PER

[sane-devel] Well known sensor

?tienne Bersac wrote: Hi, >> This is, or isn't, SANE 2 stuff. You're not going anywhere with that >> and SANE 1. > > I don't understand your sentence. I just mean renaming option in > backend, change some option type. That is mostly a matter of > implementation. And breaking stuff while at it.

[sane-devel] Well known sensor

Hi, > This is, or isn't, SANE 2 stuff. You're not going anywhere with that > and SANE 1. I don't understand your sentence. I just mean renaming option in backend, change some option type. That is mostly a matter of implementation. If you don't want to extend SANE 1 standard (like e.g. 1.2), just

[sane-devel] Well known sensor

?tienne Bersac wrote: Hi, > I propose to extend the standard to provide well known hard selected > options. Here are some exemple : This is, or isn't, SANE 2 stuff. You're not going anywhere with that and SANE 1. JB. -- Julien BLACHE

[sane-devel] Well known sensor

Hi, I forgot to talk about sensor type. Push button must be boolean representing the "pressed" state of the button. Wheel button should be either Word, fixed or string. Well known string value should be good like "color-mode", "grey-mode" for hardware mode selector. Please comment. Regards, ?t

[sane-devel] Well known sensor

Hi, SANE allow hardware selected option. I call this "sensor" for short. It can represent push button (like "scan", "cancel", "mail", etc.), wheel button (ask Allan for details), paper sensor, cover sensor, etc. Some device have blank button. Unlike software selected option, frontend *must* under

[sane-devel] Well known sensor

On Mon, Mar 17, 2008 at 3:17 PM, Julien BLACHE wrote: > ?tienne Bersac wrote: > > > Hi, > > >> This is, or isn't, SANE 2 stuff. You're not going anywhere with that > >> and SANE 1. > > > > I don't understand your sentence. I just mean renaming option in > > backend, change some option type.