Skip to content

How to prevent libinput from capturing an input device? #18

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

Closed
OOHehir opened this issue Feb 10, 2022 · 2 comments
Closed

How to prevent libinput from capturing an input device? #18

OOHehir opened this issue Feb 10, 2022 · 2 comments

Comments

@OOHehir
Copy link

OOHehir commented Feb 10, 2022

Summary: libinput is the default method for EGT of capturing inputs from devices but how does one prevent it capturing inputs from say /dev/event0 ?

Hello,
I've recently worked to add input from a resistive touchscreen input to a SAMA5D4 Xplained board via the on chip ADC. I calibrated the screen using the tslib tool ts_calibrate & ran the ts_uinput script which creates another event device for a GUI framework to capture. I found when I used this that the touchscreen performance was unsatisfactory. It appears that EGT was still capturing input from the raw inputs of the touchscreen as well as the calibrated input from ts_uinput.

I temporarily solved the issue by removing the raw input (i.e. rm /dev/event0) which resulted in satisfactory touchscreen input.

Is there a environmental option to prevent libinput capturing an event device? I've taken a look through the documents but can't see any.

Regards,

Owen

@OOHehir OOHehir changed the title How to prevent libinput from capturing input device? How to prevent libinput from capturing an input device? Feb 10, 2022
@ldesroches
Copy link
Contributor

Hi,
No there is no way to disable libinput from environment variable. This is the default input for EGT, so if an input device is handled by the libinput, it will be used.
If you want to avoid this situation, you can build EGT without the libinput support or you have to tune Application::setup_inputs() in src/app.cpp. Move m_inputs.push_back(std::make_uniquedetail::InputLibInput(*this)); somewhere else depending on the behavior you expect.

Regards,
Ludovic

@OOHehir
Copy link
Author

OOHehir commented Feb 22, 2022

OK,

I think I'll come up with a startup script to solve the issue.

@OOHehir OOHehir closed this as completed Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants