Frederik Ramm wrote:
> Hi Tom,
> I'd love to. But how do we handle things like different allowable
> resolutions, different maximum page sizes, and so on. It wouldn't be a
> problem to produce one source code file that, using "#ifdef"s, can
> produce three or four different drivers, but what options would we
> have if we were to try producing one single driver. An extra
> parameter, "--model", maybe - but how would we communicate to the SANE
> front-ends that certain settings e.g. of the "resolution" parameter
> are only available if the "model" parameter has been set to something
> specific? I doubt the current mechanism supports that.
The f/e negotiates capability with the b/e so this isn't a problem.
The standard also supports changes in capability during a session.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail firstname.lastname@example.org
This archive was generated by hypermail 2b29 : Tue Feb 27 2001 - 13:49:08 PST