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

Set input_region for surface #110

Closed
nebneb0703 opened this issue Dec 22, 2024 · 3 comments
Closed

Set input_region for surface #110

nebneb0703 opened this issue Dec 22, 2024 · 3 comments

Comments

@nebneb0703
Copy link

I'm using iced_layershell for my application. I have overridden the default style to use a transparent background but my app contains inner opaque elements. The transparent regions of my application need to be transparent to input events, corresponding to the input_region of the wl_surface. The actual gui is dynamic and therefore I cannot rely on a static layershell size. I could not find a suitable api accessible through iced_layershell.

I have two suggestions for solutions:

  1. Provide a new action capable of performing this change at runtime. The input region is part of the core wayland protocol, not the layershell protocol, so it might not entirely make sense to include it alongside other parts of this crate.
  2. Provide an escape hatch by exposing the wl_surface of the current window, such that clients can perform the set_input_region request manually.

Although not necessary for this issue, it might be useful to consider support for setting the opaque_region as well.

@Decodetalkers
Copy link
Collaborator

Yesterday this was fixed by a contributor, so maybe you can test the master branch, if it is good, I will make a release

@nebneb0703
Copy link
Author

If you are referring to #109, it does not do what I need. The events_transparent flag is a bool that applies to the whole surface, and there is no way to inject a specific region. It's also not dynamic and only applies once upon creation of the surface.

@nebneb0703
Copy link
Author

Added in #111, released in v0.13.1

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