On Thu, Nov 6, 2008 at 11:09 AM, Ilia Sotnikov <hostcc at gmail.com> wrote: > Sorry for jumping into the discussion but why don't we use > sane_get_option_descriptor() / sane_control_option() on a new > predefined option, for example, "sane-version-features", which could > be read by a frontend and if, no error occured, set to required SANE > API level (aka. additional features available), specific bitmask etc. > Doing that we could avoid any changes in already used API. And when > such an option is set by a frontend, backends could start using > additional SANE_Status. > > The implementation of such a solutions is rather simple.
I worry that a simple sane1 front-end might expose that option to the user, who might set it, then the front-end blows up anyway? But, there might be a way to set the caps on the option to hide it, and yet, still let the front-end change it? allan -- "The truth is an offense, but not a sin"
