> Here's an example of the stuff the bh backend writes:
[XML snipped]
Now I'm really starting to see why you want FRAME_ASCII or whatever...
If this is the volume of data being sent, I guess frames are the way
to go.
> Another use of the text frame might be to allow the backend to
> report its configuration. Wouldn't it be nice if the backend information
> shown in the Xsane dialog could include a little text area that simply
> displayed a textual summary of the scanner's inquired
> configuration and capabilities? This would be especially useful if
> the scanner were being accessed through saned. I don't know the mechanism
> by which the front end would ask for this, though.
Hmm. I think what you're talking about here is stuff already better
handled in SANE Options. Have you looked at that stuff in SANE 1.0?
I think it's a very powerful way to express anything a user might want
to know, and more, about the scanner's current state of mind.
Also, in SANE Options it's clear which stuff you can change, and which
stuff you can't -- there's even a way to say "The user can change this,
but only by {pressing a button, flipping a dipswitch, opening a panel}
on the scanner itself.
Nick.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com