On Sat Apr 26 05:16:37 2025 +0000, Alexandros Frantzis wrote:
Another alternative would be to encode the wl_pointer requirement in `needs_lock` and `needs_confine` in `wayland_pointer_update_constraint`. This has the extra benefit that it moves us towards better handling of dynamic removals, since we will then destroy any inert zwp constraint proxies without any special code paths (we are not completely there yet, since we don't guarantee reapplication of the cursor clip on wl_pointer removal, but it's a step in the right direction). Does such a change work for your use case?
Sure, I moved it there.