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

change the pointer of an xinput device other than the default? #15

Open
xenogenesi opened this issue Apr 28, 2024 · 0 comments
Open

change the pointer of an xinput device other than the default? #15

xenogenesi opened this issue Apr 28, 2024 · 0 comments

Comments

@xenogenesi
Copy link

xenogenesi commented Apr 28, 2024

I'm using ssh-rdp to control a PC from a tablet running Linux. ssh-rdp utilizes netevent to forward touchscreen events from the tablet to the PC, recreating the same xinput device(s). If I launch highlight-pointer on the PC or tablet, I only see it work when using the mouse. If I use the touchscreen (which is still a pointer device), I see the default X11 pointer.

edit

I run highlight-pointer --auto-hide-highlight --hide-timeout 1 --radius 10 --outline 2 on the PC, using its mouse the pointer changes as expected.

Just to have the same behavior, I run the same command on the tablet, using the tablet's mouse the pointer changes as expected.

I launch ssh-rdp and see the PC screen on the tablet. If I use the tablet's mouse, the events are forwarded, and I see the highlight-pointer pointer on the PC, but there is a normal X11 pointer overlaid (even with highlight-pointer still running on the tablet and PC). If I use the touchscreen, only the normal X11 pointer is visible. It's not clear to me whether this second X11 pointer is created on the PC or the tablet (I guess the tablet but I'm not sure), even though touchscreen events are forwarded correctly, I don't see pointers on the PC while using the tablet touchscreen.

If I run highlight-pointer after establishing the ssh-rdp connection, with the xinput devices already created, the result does not change.

I created a second pointer with xinput create second and associated it with a second mouse using xinput reattach MOUSEID POINTERID (use xinput --list for the IDs), and I see that highlight-pointer has some issues there too. The pointer appears, clicks are visible, but it doesn't move.

I tried xev to see if there were differences in the generated events but I don't see any significant one (see attached logs).

xinput-devs-on-pc.txt
mouse.log
touch.log

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

No branches or pull requests

1 participant