Re: Problems with Prisa 620S [snapscan] + BUG in xsane 0.76

From: Oliver Rauch (oliver.rauch@rauch-domain.de)
Date: Tue May 22 2001 - 09:22:15 PDT

  • Next message: Oliver Rauch: "Re: Problems with Prisa 620S [snapscan] + BUG in xsane 0.76"

    Ben Stanley wrote:
    >
    > SANE_DEBUG_SNAPSCAN=255 ./saned -d255
    >
    > and redirecting the output. I checked the size inquiry before the scan
    > data was read, and from the get_parameters call which occurs just after
    > the scan started. It seems that these two are not returning the same
    > number of lines. should they be? I can post log output if you want.

    Hi Ben,

    I took a short look at the snapscan source. There are two things:
    1) I can find out from which time the scanning related values
    are set (not the guessed ones)
    2) it is possible (looks a bit like that) the the backend does
    not respond the complete lines in param.lines but the
    remainig lines until the end of the scan. That would be a big bug.

    Can you find out about that, e.g. by adding a call to
    sane_get_parameters in xsane after sane_read ?!

    Bye
    Oliver 

    -- 
Homepage:	http://www.rauch-domain.de
sane-umax:	http://www.rauch-domain.de/sane-umax
xsane:		http://www.xsane.org
E-Mail:		mailto:Oliver.Rauch@rauch-domain.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 : Tue May 22 2001 - 10:33:56 PDT