Michael Milton

@daanzu, thanks for the cleanup! I still believe there is some work that needs to be done though. The main thing this needs is the ability to import the client...

My fairly awful workaround for now is to add this CSS: ```css .group--actions--tr { opacity: 1 !important } ```

You can also just install directly from my branch for the time being.

> I had this problem in Arch, had this exact problem with the keyboard example and solved it by adding a time.sleep(1) before sending the inputs This also worked for...

Yes, the `uinput` backend is implemented: https://github.com/moses-palmer/pynput/blob/master/CHANGES.rst#v170-2020-08-30---a-new-backend-and-many-new-features-and-bug-fixes. I believe it should automatically activate when you're on Linux, aren't on X11 and possibly you will have to run the script with...

Oh right, no. As I explain in the comment you linked to, that approach wouldn't consistently work. Rather we will have to wait for a virtual device proposal to get...

Oh it seems there has been some progress. So on the Wayland protocol side there are a few proposals but neither have been accepted: * https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/11 * https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/12 What's interesting,...

Agreed. But in theory if someone urgently wanted this feature now, I think they could implement C bindings for these unstable protocols, and you could get Python automating the mouse...

If that is the case, could we not provide a method that still does this, but takes two pointers as arguments?

Yes, making them part of the public API would be quite helpful. But also there's still the issue of the array allocation for import into Rust, ie this stuff: https://github.com/jorgecarleitao/arrow2/blob/c012c9d3095b03877bd5f610d4db746b728e9cba/examples/ffi.rs#L29-L37...