Skip to content
Advertisement

Tag: uinput

How does evdev determine whether or not to move the x11 cursor?

I’m starting to dig into the evdev api on linux for the purpose of playing around with uinput emulation. I noticed that between a joystick and a touch pad, there are different button/key event codes to distinguish between joypad button presses and mouse clicks. But both devices have event codes for ABS_X and ABS_Y axis. So how does x11 know

OSError: [Errno 19] Failed to open the uinput device: No such device

I am pretty new to raspberry and Linux. I am trying to run basic example of python library uinput on Raspbian (r Pi 3 B) with following code: I get the error: Traceback (most recent call last): File “/home/pi/Desktop/t1.py”, line 7, in uinput.REL_Y, File “/home/pi/.local/lib/python3.5/site-packages/uinput/init.py”, line 178, in init self.uinput_fd = fd or fdopen() File “/home/pi/.local/lib/python3.5/site-packages/uinput/__init.py”, line 84, in fdopen

Creating Macros With Python interfacing with Libinput

I’m running Fedora 22; and I’m trying to create a very simple keyboard macro script with uinput that will work across display servers (and in console). Following this post I figured out how to do this successfully in console and with evdev; However I also want to be able to do this through libinput (for wayland, mir and X11); does

linux uinput: simple example?

I’m having some problems getting both sides of code using uinput working. Based on Getting started with uinput: the user level input subsystem[dead link; archived] I put together the following writer (minus error handling): That seems to work, at least the full input_event structure seems to be written. I then wrote the most naive reader of events I could come

Advertisement