-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Implement version 2 of ext-idle-notify-v1 protocol #8959
Conversation
coolio, the impl looks alright to me |
gotta wait until a release is made. Ping me when the proto lands in arch |
eed9acb
to
58df01c
Compare
2d4bf06
to
8ddc936
Compare
fd70f1e
to
4630134
Compare
5df30dd
to
df2d6d6
Compare
@fufexan can you bump nix |
You are now duly pinged. Wayland-protocols 1.40 is in Arch now. |
yeah now gotta wait for mr romania to fix nix ci |
Bumped on main. |
can you rebase on main @jjramsey ? |
Signed-off-by: James Ramsey <[email protected]>
Done. |
thanks! |
Describe your PR, what does it fix/add?
This is basically a counterpart to a similar draft merge request that I did for wlroots, one that is meant to implement a revision to the ext-idle-notify protocol described in this merge request to wayland-protocols here: wayland/wayland-protocols!367
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
I did test this to make sure that it would work at least with my fork of Workrave.
Is it ready for merging, or does it need work?
This is a draft simply because the merge request for the wayland-protocols is still pending. Once it stops being pending, the commit "Temporarily allow build with w/o JJR fork of wayland-protocols" should be reverted. There is also the possibility that there will be further changes to the wayland-protocols merge request before it gets approved -- presuming of course that it gets approved at all.This should work with the wayland-protocols from commit 20bcf732a9a173ae7d437882159fb7ababb4713e or later.