Skip to content
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

protocols: Update wayland-protocols to 1.38 #761

Merged
merged 1 commit into from
Oct 14, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions wayland-protocols/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@

## Unreleased

- Bump wayland-protocols to 1.38
- New staging protocols:
* `fifo-v1`
* `commit-timing-v1`
* `xdg-system-bell-v1`

## 0.32.4 -- 2024-09-04

### Additions
Expand Down
2 changes: 1 addition & 1 deletion wayland-protocols/protocols
Submodule protocols updated from 4878e0 to 9ac1a0
47 changes: 46 additions & 1 deletion wayland-protocols/src/wp.rs
Original file line number Diff line number Diff line change
Expand Up @@ -487,7 +487,6 @@ pub mod security_context {
//! security contexts are dangerous because they can potentially allow
//! privilege escalation of a sandboxed client.


#[allow(missing_docs)]
pub mod v1 {
wayland_protocol!(
Expand All @@ -511,3 +510,49 @@ pub mod alpha_modifier {
);
}
}

#[cfg(feature = "staging")]
pub mod fifo {
//! When a Wayland compositor considers applying a content update,
//! it must ensure all the update's readiness constraints (fences, etc)
//! are met.
//!
//! This protocol provides a way to use the completion of a display refresh
//! cycle as an additional readiness constraint.

#[allow(missing_docs)]
pub mod v1 {
wayland_protocol!(
"./protocols/staging/fifo/fifo-v1.xml",
[]
);
}
}

#[cfg(feature = "staging")]
pub mod commit_timing {
//! When a compositor latches on to new content updates it will check for
//! any number of requirements of the available content updates (such as
//! fences of all buffers being signalled) to consider the update ready.
//!
//! This protocol provides a method for adding a time constraint to surface
//! content. This constraint indicates to the compositor that a content
//! update should be presented as closely as possible to, but not before,
//! a specified time.
//!
//! This protocol does not change the Wayland property that content
//! updates are applied in the order they are received, even when some
//! content updates contain timestamps and others do not.
//!
//! To provide timestamps, this global factory interface must be used to
//! acquire a `wp_commit_timing_v1` object for a surface, which may then be
//! used to provide timestamp information for commits.

#[allow(missing_docs)]
pub mod v1 {
wayland_protocol!(
"./protocols/staging/commit-timing/commit-timing-v1.xml",
[]
);
}
}
13 changes: 13 additions & 0 deletions wayland-protocols/src/xdg.rs
Original file line number Diff line number Diff line change
Expand Up @@ -217,3 +217,16 @@ pub mod toplevel_icon {
);
}
}

#[cfg(feature = "staging")]
pub mod system_bell {
//! This global interface enables clients to ring the system bell.

/// Version 1
pub mod v1 {
wayland_protocol!(
"./protocols/staging/xdg-system-bell/xdg-system-bell-v1.xml",
[]
);
}
}
Loading