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 provide a RFC for backend developer in order to have backend consistent and sensor usable by frontend, without end user interaction to assign sensor to action. 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 ?? We definitely need semantic in sensors. Regards, ?tienne.
