Incorrect hide/display policies
Opened this issue · 3 comments
What is this an issue for exactly?
Issue templates are there for a reason, please use them!
Unless I've vastly misunderstood the underlying technologies, we quickly run into the issue of wanting a state that doesn't exist.
The state where we get alerted to mouse move/mouse click/mouse in/mouse out will also consume those events. I don't see any way to monitor the events and still allow the application below them to see them.
Mouse out events trigger the moment something causes the mouse to be outside the window, which as you say happens as soon as we set window as untouchable. If we simply drew blank and kept the previous mask we'd consume pointer events, only allowing user to see through but not click.
Did you test this? This changes nothing on my setup.
The event continues on in GTK, gets to the end, but is still consumed in window-manager context and doesn't continue out to the next window.