Re: [sane-devel] Interactive use of scanner buttons

2021-12-08 Thread Ralph Little
Hi, As an aside, some discussion around this was had before. There is an issue in the SANE standard repo where we might decide on something: https://gitlab.com/sane-project/standard/-/issues/7 Cheers, Ralph On Wed, Dec 8, 2021 at 10:23 AM Paul Wolneykien wrote: > 3 декабря 2021 г. 19:00:25

Re: [sane-devel] Interactive use of scanner buttons

2021-12-08 Thread Paul Wolneykien
3 декабря 2021 г. 19:00:25 GMT+03:00, Paul Wolneykien пишет: >В Fri, 03 Dec 2021 10:34:05 -0500 >ryni...@ryniker.org пишет: >> A callback mechanism provides a framework that can naturally avoid >> missed button events, and can support variations such as capture of >> "button down" and "button

Re: [sane-devel] Interactive use of scanner buttons

2021-12-04 Thread Jörn-Ingo Weigert
Usually, those scan to pc functionality require either a (anonymous) SMB/ FTP folder or prop. driver on the target PC. If your scanner is connected to the network, try to reach the web interface of the browser by it's IP Address to configure your scan buttons. Perry Hutchison via sane-devel

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Perry Hutchison via sane-devel
A data point: The Canon MF4880dw -- a multifunction device with network and USB interfaces -- has two buttons, labelled Scan->PC1 and Scan->PC2, which seem as if they could be of interest to sane. When I attempt to configure one of those buttons using the front panel, selecting "Network

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Paul Wolneykien
В Fri, 3 Dec 2021 11:53:09 -0500 "m. allan noah" пишет: > > As far as I know, SANE provides exclusive access to the scanner > > for one client only. So, we can run a poller or a frontend, but not > > both. That's why I would like to see the polling process running > > "inside" backend (be

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread m. allan noah
On Fri, Dec 3, 2021 at 11:39 AM Paul Wolneykien wrote: > > В Fri, 3 Dec 2021 11:08:23 -0500 > "m. allan noah" пишет: > > > On Fri, Dec 3, 2021 at 9:33 AM Paul Wolneykien > > wrote: > > > > > В Fri, 3 Dec 2021 09:02:43 -0500 > > > "m. allan noah" пишет: > > > > > > > Many backends are single

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Paul Wolneykien
В Fri, 3 Dec 2021 11:08:23 -0500 "m. allan noah" пишет: > On Fri, Dec 3, 2021 at 9:33 AM Paul Wolneykien > wrote: > > > В Fri, 3 Dec 2021 09:02:43 -0500 > > "m. allan noah" пишет: > > > > > Many backends are single threaded currently, so this would be a > > > pretty invasive change. > > >

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread m. allan noah
On Fri, Dec 3, 2021 at 9:33 AM Paul Wolneykien wrote: > В Fri, 3 Dec 2021 09:02:43 -0500 > "m. allan noah" пишет: > > > Many backends are single threaded currently, so this would be a pretty > > invasive change. > > But that's not a required change, isn't it? If a backend isn't ready > for

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Wilhelm Meier via sane-devel
On 03.12.21 16:54, Paul Wolneykien wrote: > В Fri, 3 Dec 2021 15:19:16 +0100 > Wilhelm Meier via sane-devel пишет: > >> There is this old project of mine called "scanbd", the "scanner button >> daemon". There wasn't low / no activity in the last year(s), but it is >> still functional because it

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Paul Wolneykien
В Fri, 03 Dec 2021 10:34:05 -0500 ryni...@ryniker.org пишет: > "m. allan noah" wrote on Fri, 3 Dec 2021 > 09:02:43 -0500: > > >Frankly, polling over the network once per second is not that much > >traffic, and certainly easier to implement. > > Yes, but it is wrong. Someone will decide it

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Paul Wolneykien
В Fri, 3 Dec 2021 15:19:16 +0100 Wilhelm Meier via sane-devel пишет: > There is this old project of mine called "scanbd", the "scanner button > daemon". There wasn't low / no activity in the last year(s), but it is > still functional because it is strictly POSIX conform. I've seen it. And I

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Wilhelm Meier
There is this old project of mine called "scanbd", the "scanner button daemon". There wasn't low / no activity in the last year(s), but it is still functional because it is strictly POSIX conform. If anyone is interested in taking care of that, I would be very happy.

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Wilhelm Meier via sane-devel
There is this old project of mine called "scanbd", the "scanner button daemon". There wasn't low / no activity in the last year(s), but it is still functional because it is strictly POSIX conform. If anyone is interested in taking care of that, I would be very happy.

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Paul Wolneykien
В Fri, 3 Dec 2021 09:02:43 -0500 "m. allan noah" пишет: > Many backends are single threaded currently, so this would be a pretty > invasive change. But that's not a required change, isn't it? If a backend isn't ready for it, it just should not add SANE_CAP_DYNAMIC to the options. > Frankly,

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Kelly Price
Well, that and if the access to the scanner is locked at the saned level, polling isn't going to tie it up and saned can always return a "We're busy scanning" signal. On Fri, Dec 3, 2021 at 9:03 AM m. allan noah wrote: > > Many backends are single threaded currently, so this would be a pretty >

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread m. allan noah
Many backends are single threaded currently, so this would be a pretty invasive change. Frankly, polling over the network once per second is not that much traffic, and certainly easier to implement. allan On Fri, Dec 3, 2021 at 8:50 AM Paul Wolneykien wrote: > В Thu, 2 Dec 2021 17:29:13 -0800

Re: [sane-devel] Interactive use of scanner buttons

2021-12-03 Thread Paul Wolneykien
В Thu, 2 Dec 2021 17:29:13 -0800 Ralph Little пишет: > However, regular polling can be > detrimental as a general feature. One commentator suggested that over > a network, this could become an unnecessary bandwidth hog. In SANE we > would want to add polling features in a generic fashion and

Re: [sane-devel] Interactive use of scanner buttons

2021-12-02 Thread Andy Bennett
Hi, So, for scanning books, it would be nice to be able to control such a frontend as XSane with the scanner's hardware buttons. Because most of the time you can reach the hardware button even if you handle the book using both hands (however, a configurable delay after the button is pressed

Re: [sane-devel] Interactive use of scanner buttons

2021-12-02 Thread Kelly Price
Allan hit it there. You may have buttons that are exposed as USB keyboard or HID devices, or it may piggyback on the protocol being used for just scanning. You may need a system notification app on your desktop that integrates XSane (probably a localized saned over Unix sockets). That said... I

Re: [sane-devel] Interactive use of scanner buttons

2021-12-02 Thread m. allan noah
There is a great deal of variation between scanners and backends regarding what buttons are available and how they are exposed. You also have the exclusive device access problem. In the end, I think you need a new frontend, or modifications to an existing one, rather than a separate monitor.

Re: [sane-devel] Interactive use of scanner buttons

2021-12-02 Thread Ralph Little
Hi, On 2021-12-02 2:35 p.m., Paul Wolneykien wrote: As I can see, XSane doesn't poll the scanner's hardware buttons. And if I understand the scanbd manual right, the daemon locks the SANE interface to the scanner until a button is pressed, and then gives exclusive access to the scanner for

[sane-devel] Interactive use of scanner buttons

2021-12-02 Thread Paul Wolneykien
Hi! As I can see, XSane doesn't poll the scanner's hardware buttons. And if I understand the scanbd manual right, the daemon locks the SANE interface to the scanner until a button is pressed, and then gives exclusive access to the scanner for the frontend. So, the daemon is primarily for