11–20 of 67 posts
I know, because I wanted to automate a GUI task using PyAutoGUI and it wouldnt work on wayland no matter what.
Slightly related. On wayland based linux desktops this would never work because an app is not allowed to hijack the mouse pointer to dispatch events. I believe only the compositor is allowed to do that. I know, because I wanted to automate a GUI task using PyAutoGUI and it wouldnt work on wayland no matter what.
Github has no source code.
Pass for me.
Slightly related. On wayland based linux desktops this would never work because an app is not allowed to hijack the mouse pointer to dispatch events. I believe only the compositor is allowed to do that. I know, because I wanted to automate a GUI task using PyAutoGUI and it wouldnt work on wayland no matter what.
My problem with these types of apps will always be that most software it interacts with will unfortunately be designed without accessibility in mind. I've trialed a handful of these mouse-less programs before and I always run into the same hurdles. E.g. where one or more of my apps have sliders which I can't interact with using clicks instead of drags (so I can't interact with it at all), or needing to click things l…
I've had a poor experience with accessibility apis, they're clunky, slow, and unpredictable, and as you said many apps aren't built with accessibility in mind. With computer vision you don't have to worry about that.
This might sound strange, but the cv system in Neverclick actually runs significantly faster than UI Automation (which is the accessibility api on windows) in nearly all of my personal tests. I can't believe that accessibility apis are so poorly optimized that raw pixel analysis is faster lol. Also, I have users that use Neverclick on 10 year old hardware and they tell me that the cv runs instantly whereas UI Automation is super laggy for them.
Also, accessibility apis typically don't give you useful bounding boxes for text in text editors, this is another advantage of the cv approach.
I really wish the title of the post was "Desktop application for performing mouse actions with your keyboard using computer vision" so that it's more obvious that it uses cv, although it's my fault since the current title is how I have it in the readme and they probably just copied that.
Slightly related. On wayland based linux desktops this would never work because an app is not allowed to hijack the mouse pointer to dispatch events. I believe only the compositor is allowed to do that. I know, because I wanted to automate a GUI task using PyAutoGUI and it wouldnt work on wayland no matter what.
QMK-powered keyboards can do this out of the box
thanks for the heads up, I have a keychron gathering dust at home, so I'll test this later on. favved the thread anyway, since I'm interested, but will wait for the macOS version.