> > > Nope, not at this point. Printing messages wouldn't be hard to do,
> > > but dialog boxes are a bit trickier because sometimes there is no user
> > > to dialog with. What exactly did you have in mind?
>
> It might be useful if there were a way for the backend to say to the
> frontend "I have a status message",
This is easy. SANE supports text fields, and those can be set from the
backend easily be requesting a full option reload.
> or "I have a yes/no/cancel question",
Please if at all possible - avoid that. This is really bad for
scripting ...
> aren't quite enough, because the backend might want to ask a question
> in the middle of an API function call, and then the call has to exit
> and somehow be restarted with the information it didn't have. So what
> about frontends supplying callback functions to the backend at
> initialization time? For example, a callback that answers a
> yes/no/cancel question might have prototype
This complicates quite a bunch of things. It is _really_ needed ?
Could you give an example ?
> Obviously either approach involves an API change so it would have to
> be for a future version.
Regarding returning status messages, this can easily be solved without
changing API.
CU,Andy
-- = Andreas Beck | Email : <andreas.beck@ggi-project.org> =
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com