Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better touchscreen detection #17

Open
Salamek opened this issue May 9, 2021 · 1 comment
Open

Better touchscreen detection #17

Salamek opened this issue May 9, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@Salamek
Copy link
Owner

Salamek commented May 9, 2021

Current impl sux, use udevadm info --export-db ?
match devices with ID_INPUT_TOUCHSCREEN=1

@Salamek Salamek added the enhancement New feature or request label May 9, 2021
@Salamek
Copy link
Owner Author

Salamek commented Jul 25, 2023

Hmm i had look on this, and using udev to find a touchscreen kinda work... but some touchscreens do NOT set ID_INPUT_TOUCHSCREEN=1 but ID_INPUT_MOUSE=1 and then we fail to find them... also there is no way to match dbus device with xinput listed devices... so current way of finding touchscreen (matching names to xinput devices) is hot garbage but it provides best results for now... maybe look on this again when we switch to wayland and libinput?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant