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

From: Ben Stanley (bds02@uow.edu.au)
Date: Tue May 22 2001 - 15:56:52 PDT

  • Next message: Mick Barry: "Re: Q: windows port"

    Oliver Rauch wrote:

    >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 ?!
    >
    Here you go:

    [xsane] preview_scan_start
    [xsane] xsane_clear_histogram
    [xsane] xsane_clear_histogram
    [xsane] xsane_set_sensitivity
    [xsane] preview_expose_event_handler_start
    [xsane] preview_draw_selection
    [xsane] preview_expose_event_handler_end
    [xsane] preview_draw_selection
    [xsane] preview_draw_rect [0.75 0.75 211.23 122.96]
    [xsane] preview_transform_coordinates_device_to_window
    [xsane] preview_get_scale_device_to_window: scale = 1.300926, 1.300926
    [xsane] preview[0.75 0.75 211.23 122.96] -> window[0.98 0.98 274.79 159.97]
    [xsane] preview_get_memory
    [xsane] preview_read_image_data
    [xsane] scan lines after sane_read: 843.[xsane] scan width after
    sane_read: 637.[xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] scan lines after sane_read: 838.[xsane] scan width after
    sane_read: 637.[xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] scan lines after sane_read: 834.[xsane] scan width after
    sane_read: 637.[xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] scan lines after sane_read: 830.[xsane] scan width after
    sane_read: 637.[xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y
    [xsane] preview_increment_image_y

    Looks like your theory is confirmed. Not sure I know what to do about it
    yet... I mean, I know the backend has to be fixed, but I'm not in a
    position to be able to do it yet :-).

    Ben. 

    --
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 - 15:56:52 PDT