Hmm - as reads are normally "expensive" operations, too (compared to
an option setting), we might simply want to re-read all options after
a read ...
> Peter> Oh yes, another one, though I suspect I know the answer to
> Peter> this one. Is there any way for a backend to put up it's own
> Peter> dialog boxes for warnings or confirmations?
> 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?
Yes. For scripting applications, there should not be "unpredictable"
questions popping up. I got very upset at several windows programs
doing that, when I tried to make macro-recorder scxripts for them
for a few common tasks one of my customers has to do ...
> As a general comment, I fully expect that we'll have to make some
> adjustments to the SANE API to better support digital cameras. I'd
> suggest that, for now, you hack around problems you encounter as your
> progresses. Then, once we're confident we understand what's needed to
> support cameras well, we can then add the missing stuff to the API.
> Sounds reasonable?
Yes ... there is already that "transparent data returned" change pending,
and we should check further on what implications such backends may bring
and then bring out SANE API 1.1 or something.
-- = Andreas Beck | Email : <email@example.com> =
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail firstname.lastname@example.org