?tienne Bersac <bersace03 at gmail.com> 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. > Currently, SANE backend sensor implementation mean : "Something happen, > guess what". E.g. plustek backend provide "button 0" to "button 4", both > integer with value 0. Once a button is pushed, value is 1. How can a > frontend know what does mean "button 0"=1 ? Can guess "button 0" > pressed. But what next ?? 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 standard accross all the hardware. It's not a trivial problem to fix, as past discussions have shown. JB. -- Julien BLACHE <http://www.jblache.org> <jb at jblache.org> GPG KeyID 0xF5D65169
