Tiny Core Extensions > TCE News

AutoCursor extension submitted

<< < (6/7) > >>

jazzbiker:
Hi, Rich!

Does to get more (the most?) reliable device classifier we need to ask libinput?
Then the sequence became a little bit longer.
1. Get list of events
2. If device is keyboard, assign 'h' cmd and go on. else
3. If device is of some kind graphical manipulator (including tablets, joystick and even accelerators?) then capture its name
4. Associate this name with X device id, using "xinput list"
5. Capture device properties
6. Determine device role depending on "absolute" ('h' command) or "relative" ('s' command) property presence.

Such way may appear to be unambiguous. What's Your opinion?

Rich:
Hi jazzbiker

--- Quote from: jazzbiker on February 05, 2021, 12:21:00 PM ---Does to get more (the most?) reliable device classifier we need to ask libinput? ...
--- End quote ---
I don't think so. I would suggest this might be a Lubuntu issue. If you look at your reply #23, you'll see Tinycore listed
only the correct device. Maybe Lubuntu needs a udev rule (see reply #22) similar to:

--- Code: ---ACTION=="change", KERNEL=="event[0-9]*", ENV{ID_VENDOR_ID}=="0002", \
ENV{ID_MODEL_ID}=="0007", ENV{ID_INPUT_TOUCHSCREEN}=""
--- End code ---

Your script, because it looks at touchpad before touchscreen, would return the correct result.

Rich:
Hi jazzbiker
The programs  usage  page did not list all of the command line switches. This has been corrected,
The updated extension has been posted.

jazzbiker:
Hi, Rich!

Thanks for the update! I didn't tried yet AutoCursor under Lubuntu, but I hope it will run without problems under another Linuxes.

jazzbiker:
Hi, Rich!

You didn't submitted AutoCursor for TC12, so I copied tcz from TC10 tce directory. libXfixes was last updated 2017/02/20, I think this is reliable. Am I right?

Navigation

[0] Message Index

[#] Next page

[*] Previous page