John Vickers wrote:
> Hi.
>
> I had a bit more of a poke around, and I think the problem is in xsane.
>
> (After making sure I really was linking with the sane I thought
> I was linking with...)
>
> xsane uses quite different code for the preview resolution slider
> and for the main resolution slider.
>
> For the preview slider, the xsane resets the slider value to the
> resolution value returned by the backend, so that a subsequent
> change to the slider value, via cursor keys or mouse clicks
> is relative to the valuye returned by the backend.
>
> For the main resolution slider, the slider value is never reset.
>
> HTH. I'll do some more digging. But this GUI stuff is a bit high level
> for me. Can't you write it in VHDL ? ;-)
>
> John.
>
> Karl Heinz Kremer wrote:
> >
> > Hmmm... The Epson backend uses a range for both the scan and
> > preview resolution. What is the "recommended" way of handling
> > the resolution list? I've checked all the backends in the CVS
> > and I see word lists, string lists, and ranges. I have the
> > feeling that I should change this... Oliver, do you have
> > any advise on which of the lists is more useable from a
> > frontend perspective?
> >
Hello Karl Heinz,
the sane standard defines only one "resolution" as well known option.
It does not make sense to have a "preview resolution" option because
the frontend has to set the correct resolution in each case and like defined
in the standard xscanimage and xsane do set the option "resolution".
If the preview resolution option is removed from the epson backend
everything will work fine.
Bye
Oliver
-- 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 majordomo@mostang.com
This archive was generated by hypermail 2b29 : Sat Feb 19 2000 - 04:25:36 PST