[sane-devel] scanner buttons, was: Simplified installation procedure for Redhat Fedora Linux 1.0 and Epson 1670 scanner, also a report of a bug?

[Henning Meier-Geinitz]

Hi,

On Fri, Jul 09, 2004 at 01:20:14AM +0200, Rene Rebe wrote:
> When the state is read by the application, it should be in some way
> reset. Any idea how this fits into the proposed ideas - especially if
> we have single options?

Once the option has been read by the frontend, reset the value to "not
pressed" in the backend?

> There is the disadvantage that is is harder to flush the state. If all
> would be in a mask the next read could just reset it ...

Why not reset directly after the read i.e. the next read gets "button
not pressed"? If we use single options the difference is that
different buttons can be pressed at the same time (or directly after
each other). E.g. if I press the "copy" button, the scanning starts
and now I press the "scan" button I'd expect the image to be also
scanned (after the end of the first scan). If we reset the bitmask
completely the second button press is ignored.

I don't sue buttons so I don't really know what the expected behaviour
is.

Bye,
  Henning