A client might delete its pointer lock/confinement object. This is supposed to
directly remove the pointer lock/confinement in KWin, but did not explicitly
until now.
BUG: 388885
davidedmundson |
KWin |
A client might delete its pointer lock/confinement object. This is supposed to
directly remove the pointer lock/confinement in KWin, but did not explicitly
until now.
BUG: 388885
Tested manually with Neverball, Nexuiz and the new pointer constraints test
application. The pointer constraints autotest is also appended.
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
autotests/integration/pointer_constraints_test.cpp | ||
---|---|---|
255 | On the resource there should be an unbound signal. |
autotests/integration/pointer_constraints_test.cpp | ||
---|---|---|
255 | Not sure how I get the resource of the proxy, but I'm spying now on the KWayland::Server::SurfaceInterface::pointerConstraintsChanged signal, what also works. |
One minor request.
autotests/integration/pointer_constraints_test.cpp | ||
---|---|---|
255 | generally speaking in kwayland terms: Resource == the thing on the server So "resource of the proxy" is confusing. IMHO you're now watching a better signal than unbound, as it happens after the pointers are cleared in surface_interface, but please rename the spy to something more fitting. |