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

With multiple displays connected, input will only be generated on the primary display #264

Open
Sandr-aa opened this issue Mar 29, 2024 · 2 comments

Comments

@Sandr-aa
Copy link

I have added an secondary virtual display with this method: https://www.reddit.com/r/linux_gaming/comments/119njgz/how_could_i_create_a_virtual_monitor_under/?rdt=45546

However touch/stylus input is only generated on the primary display when the weylus webinterface is showing the second display, I am also using wayland.

@Sandr-aa Sandr-aa changed the title With multiple displays are connected, input will only be generated on the primary display With multiple displays connected, input will only be generated on the primary display Mar 29, 2024
@crizmo
Copy link

crizmo commented May 23, 2024

As in lets say you have broweser open on your second display and when you do something there , like click on a tab it shows the output there and on the primary display as well right ?

cause its like that for me and i dont want that
the ouput should be strictly showed on the display where i clicked

@H-M-H
Copy link
Owner

H-M-H commented Oct 17, 2024

Thanks for the report! Unfortunately Wayland makes things more complicated and proper input mapping can not be done automatically. Please try the latest build here: https://github.com/H-M-H/Weylus/actions/runs/11365577130#artifacts

The web interface now includes an additional button Custom Input Area if you enable the checkbox for Wayland support. Like this you can define the input mapping yourself. Also not that if the input is mapped to only one display, you may need to change that in the gnome settings. I use KDE myself and there is a setting to map touch input to a specific screen.

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

3 participants