Henning Meier-Geinitz wrote:
> I see. So maybe we can just add some sort of callback mechanism
> sane_set_message_callback (message_call_back_function_pointer m)
> So with using this, the frontend tells the backend that it can handle
we should not add such "hacks" to the existing sane standard.
We can think about adding a callback to sane-2.0, in that case
the frontend does not need to tell the backend what it can do
(SANE defines that a sane-2.0 backend will not work with a 1.0 frontend).
> In your case you could pop up the message "Remaining time for warm-up:
> xx seconds. Do you want to scan immediately or wait for warm-up?"
For this the backend should define a bool option
"fast warmup" or a range "warmup time (1..300 sec)".
-- Homepage: http://www.wolfsburg.de/~rauch sane-umax: http://www.wolfsburg.de/~rauch/sane/sane-umax.html xsane: http://www.wolfsburg.de/~rauch/sane/sane-xsane.html E-Mail: mailto:Oliver.Rauch@Wolfsburg.DE
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail email@example.com
This archive was generated by hypermail 2b29 : Thu Nov 09 2000 - 11:22:36 PST