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

If the app absolute position is outside physical screen, pointer input is not working #46

Closed
KosmX opened this issue Jul 30, 2024 · 3 comments

Comments

@KosmX
Copy link

KosmX commented Jul 30, 2024

For example if the screen is at 1000x0 (infinite size) and satellite reports a window position of 0x0, XWayland will always report a pointer position inside the physical screen (X >= 1000)

possible solutions i think:

  • lie to XWayland, report a massive display from 0x0 with size including the whole setup
  • move window inside physical screen (i don't know if wayland compositors provide an absolute window position)

I might try to do something about this.
This issue may be the same as #15

@Supreeeme
Copy link
Owner

This should have already been fixed by d3a46b7

@KosmX
Copy link
Author

KosmX commented Jul 31, 2024

It is not fixed on main branch as of writing this.

  • arch
  • Hyprland noX (because if XWayland in Hyprland dies, it can kill the whole compositor)

@Supreeeme
Copy link
Owner

Finally got around to looking at this - it seems that satellite utilizes the wl_output positioning but Hyprland only updates the xdg_output positioning, which is fair given that it seems like xdg_output is supposed to be preferred to wl_output anyway, and Xwayland also acts as such. Shouldn't be too hard to fix.

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

2 participants