Am 31.03.2015 um 18:26 schrieb RainerF:
Wilhelm,
I wasn't sure what you meant with
Wilhelm Meier-2 wrote
So please change the bool-expression in this if() to true and test,
please.
So I commented the outer if statement
// if ((st-opts[si].from_value.num_value ==
Am 31.03.2015 um 15:43 schrieb RainerF:
Wilhelm,
thank you for taking the time to look into these issues. Following your
advise I had a look into the source code and tried to understand, what
happens in case, when e.g. button 3 is pressed and compared the logs
with the information by
Wilhelm,
thank you for taking the time to look into these issues. Following your
advise I had a look into the source code and tried to understand, what
happens in case, when e.g. button 3 is pressed and compared the logs with
the information by pressing e.g. button 4 (log file excerpt - see
Wilhelm,
I wasn't sure what you meant with
Wilhelm Meier-2 wrote
So please change the bool-expression in this if() to trueand test, please.
So I commented the outer if statementand recompiled. That's working now for
all buttons.
Thanks a lot for your efforts!
Kind regards,
Rainer
--
View
this line is printed in the logging data. The backend seems to work properly
as well. Its just a guess: either there is no value change for button 1 and
4 or the values are not numerical. (?)
I assume the hardware is ok as well, because I used the old scanbuttend with
Debian Wheezy so far, and
Am 30.03.2015 um 12:17 schrieb RainerF:
I tried to configure scanbd for an EPSON Perfection 1670 on a Raspbian
Jessie system. First I installed scanbd form the Raspbian package
repository, but this version seems to be compiled for sane backends
support only, which don't recognise button
I tried to configure scanbd for an EPSON Perfection 1670 on a Raspbian Jessie
system. First I installed scanbd form the Raspbian package repository, but
this version seems to be compiled for sane backends support only, which
don't recognise button pressed events on my scanner. Then I compiled
