Ottatop

Agree that 1 is bad, I think any solution is *required* to process all events. With 2, 3, 4, and 5, while we stabilize the ids somewhat, we still run...

Ye we can roll with this impl. The event buffer being unbounded is fine, we can change it if it ever becomes an issue.

Yea let's push off figuring out throttling/other handling for spammy signals. This problem is probably going to affect other things like gesture binds in the future so I'd like to...

Yes, PR for the event handling changes would be good

The current behavior is intended. Any defined ordering of windows would annoy one person or another: - Tiled -> Fullscreen -> Floating makes it impossible to view a fullscreen window...

> I was reading the second part as that nothing that is not part of the same surface tree should be visible. > ["other screen content not part of the...

Oh wasn't paying attention to which issue that pr closed

> Without it, the monitor activated, but no signal was fired. The only thing that causes `set_output_enabled` currently is [zwlr_output_configuration_v1::{enable_head,disable_head}](https://wayland.app/protocols/wlr-output-management-unstable-v1#zwlr_output_configuration_v1). Enabling the output when the mode is set is not...

> When my monitor turns on again, it goes here: https://github.com/pinnacle-comp/pinnacle/blob/main/src/backend/udev.rs#L1068 Which maps everything and basically turns it on (starts showing stuff). But pinnacle still thinks that it is not...

I'd rather not build in specific sloppy focus models because a) it doesn't allow finer control, and b) there would be multiple ways to have sloppy focus and that's less...