//! Interoperability library for Rust Windowing applications. //! //! This library provides standard types for accessing a window's platform-specific raw window //! handle and platforms display handle. This does not provide any utilities for creating and //! managing windows; instead, it provides a common interface that window creation libraries (e.g. //! Winit, SDL) can use to easily talk with graphics libraries (e.g. gfx-hal). //! //! ## Safety guarantees //! //! Please see the docs of [`HasWindowHandle`] and [`HasDisplayHandle`]. //! //! ## Platform handle initialization //! //! Each platform handle struct is purposefully non-exhaustive, so that additional fields may be //! added without breaking backwards compatibility. Each struct provides an `empty` method that may //! be used along with the struct update syntax to construct it. See each specific struct for //! examples. //! //! ## Display Handles //! //! Some windowing systems use a separate display handle for some operations. The display usually //! represents a connection to some display server, but it is not necessarily tied to a particular //! window. See [`RawDisplayHandle`] for more details.
#[cfg(feature = "alloc")] externcrate alloc;
#[cfg(feature = "std")] externcrate std;
mod android; mod appkit; mod borrowed; mod haiku; mod redox; mod uikit; mod unix; mod web; mod windows;
/// Window that wraps around a raw window handle. /// /// # Safety /// /// Users can safely assume that pointers and non-zero fields are valid, and it is up to the /// implementer of this trait to ensure that condition is upheld. /// /// Despite that qualification, implementers should still make a best-effort attempt to fill in all /// available fields. If an implementation doesn't, and a downstream user needs the field, it should /// try to derive the field from other fields the implementer *does* provide via whatever methods the /// platform provides. /// /// The exact handles returned by `raw_window_handle` must remain consistent between multiple calls /// to `raw_window_handle` as long as not indicated otherwise by platform specific events. #[deprecated = "Use `HasWindowHandle` instead"] pubunsafetrait HasRawWindowHandle { fn raw_window_handle(&self) -> Result<RawWindowHandle, HandleError>;
}
#[allow(deprecated)] unsafeimpl<T: HasWindowHandle + ?Sized> HasRawWindowHandle for T { fn raw_window_handle(&self) -> Result<RawWindowHandle, HandleError> { self.window_handle().map(Into::into)
}
}
/// A window handle for a particular windowing system. /// /// Each variant contains a struct with fields specific to that windowing system /// (e.g. [`Win32WindowHandle`] will include a [HWND], [`WaylandWindowHandle`] uses [wl_surface], /// etc.) /// /// [HWND]: https://learn.microsoft.com/en-us/windows/win32/winmsg/about-windows#window-handle /// [wl_surface]: https://wayland.freedesktop.org/docs/html/apa.html#protocol-spec-wl_surface /// /// # Variant Availability /// /// Note that all variants are present on all targets (none are disabled behind /// `#[cfg]`s), but see the "Availability Hints" section on each variant for /// some hints on where this variant might be expected. /// /// Note that these "Availability Hints" are not normative. That is to say, a /// [`HasWindowHandle`] implementor is completely allowed to return something /// unexpected. (For example, it's legal for someone to return a /// [`RawWindowHandle::Xlib`] on macOS, it would just be weird, and probably /// requires something like XQuartz be used). #[non_exhaustive] #[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)] pubenum RawWindowHandle { /// A raw window handle for UIKit (Apple's non-macOS windowing library). /// /// ## Availability Hints /// This variant is likely to be used on iOS, tvOS, (in theory) watchOS, and /// Mac Catalyst (`$arch-apple-ios-macabi` targets, which can notably use /// UIKit *or* AppKit), as these are the targets that (currently) support /// UIKit.
UiKit(UiKitWindowHandle), /// A raw window handle for AppKit. /// /// ## Availability Hints /// This variant is likely to be used on macOS, although Mac Catalyst /// (`$arch-apple-ios-macabi` targets, which can notably use UIKit *or* /// AppKit) can also use it despite being `target_os = "ios"`.
AppKit(AppKitWindowHandle), /// A raw window handle for the Redox operating system. /// /// ## Availability Hints /// This variant is used by the Orbital Windowing System in the Redox /// operating system.
Orbital(OrbitalWindowHandle), /// A raw window handle for Xlib. /// /// ## Availability Hints /// This variant is likely to show up anywhere someone manages to get X11 /// working that Xlib can be built for, which is to say, most (but not all) /// Unix systems.
Xlib(XlibWindowHandle), /// A raw window handle for Xcb. /// /// ## Availability Hints /// This variant is likely to show up anywhere someone manages to get X11 /// working that XCB can be built for, which is to say, most (but not all) /// Unix systems.
Xcb(XcbWindowHandle), /// A raw window handle for Wayland. /// /// ## Availability Hints /// This variant should be expected anywhere Wayland works, which is /// currently some subset of unix systems.
Wayland(WaylandWindowHandle), /// A raw window handle for the Linux Kernel Mode Set/Direct Rendering Manager /// /// ## Availability Hints /// This variant is used on Linux when neither X nor Wayland are available
Drm(DrmWindowHandle), /// A raw window handle for the Linux Generic Buffer Manager. /// /// ## Availability Hints /// This variant is present regardless of windowing backend and likely to be used with /// EGL_MESA_platfrom_gbm or EGL_KHR_platfrom_gbm.
Gbm(GbmWindowHandle), /// A raw window handle for Win32. /// /// ## Availability Hints /// This variant is used on Windows systems.
Win32(Win32WindowHandle), /// A raw window handle for WinRT. /// /// ## Availability Hints /// This variant is used on Windows systems.
WinRt(WinRtWindowHandle), /// A raw window handle for the Web. /// /// ## Availability Hints /// This variant is used on Wasm or asm.js targets when targeting the Web/HTML5.
Web(WebWindowHandle), /// A raw window handle for a Web canvas registered via [`wasm-bindgen`]. /// /// ## Availability Hints /// This variant is used on Wasm or asm.js targets when targeting the Web/HTML5. /// /// [`wasm-bindgen`]: https://crates.io/crates/wasm-bindgen
WebCanvas(WebCanvasWindowHandle), /// A raw window handle for a Web offscreen canvas registered via [`wasm-bindgen`]. /// /// ## Availability Hints /// This variant is used on Wasm or asm.js targets when targeting the Web/HTML5. /// /// [`wasm-bindgen`]: https://crates.io/crates/wasm-bindgen
WebOffscreenCanvas(WebOffscreenCanvasWindowHandle), /// A raw window handle for Android NDK. /// /// ## Availability Hints /// This variant is used on Android targets.
AndroidNdk(AndroidNdkWindowHandle), /// A raw window handle for Haiku. /// /// ## Availability Hints /// This variant is used on HaikuOS.
Haiku(HaikuWindowHandle),
}
/// Display that wraps around a raw display handle. /// /// # Safety /// /// Users can safely assume that pointers and non-zero fields are valid, and it is up to the /// implementer of this trait to ensure that condition is upheld. /// /// Despite that qualification, implementers should still make a best-effort attempt to fill in all /// available fields. If an implementation doesn't, and a downstream user needs the field, it should /// try to derive the field from other fields the implementer *does* provide via whatever methods the /// platform provides. /// /// The exact handles returned by `raw_display_handle` must remain consistent between multiple calls /// to `raw_display_handle` as long as not indicated otherwise by platform specific events. #[deprecated = "Use `HasDisplayHandle` instead"] pubunsafetrait HasRawDisplayHandle { fn raw_display_handle(&self) -> Result<RawDisplayHandle, HandleError>;
}
#[allow(deprecated)] unsafeimpl<T: HasDisplayHandle + ?Sized> HasRawDisplayHandle for T { fn raw_display_handle(&self) -> Result<RawDisplayHandle, HandleError> { self.display_handle().map(Into::into)
}
}
/// A display server handle for a particular windowing system. /// /// The display usually represents a connection to some display server, but it is not necessarily /// tied to a particular window. Some APIs can use the display handle without ever creating a window /// handle (e.g. offscreen rendering, headless event handling). /// /// Each variant contains a struct with fields specific to that windowing system /// (e.g. [`XlibDisplayHandle`] contains a [Display] connection to an X Server, /// [`WaylandDisplayHandle`] uses [wl_display] to connect to a compositor). Not all windowing /// systems have a separate display handle (or they haven't been implemented yet) and their variants /// contain empty structs. /// /// [Display]: https://www.x.org/releases/current/doc/libX11/libX11/libX11.html#Display_Functions /// [wl_display]: https://wayland.freedesktop.org/docs/html/apb.html#Client-classwl__display /// /// # Variant Availability /// /// Note that all variants are present on all targets (none are disabled behind /// `#[cfg]`s), but see the "Availability Hints" section on each variant for /// some hints on where this variant might be expected. /// /// Note that these "Availability Hints" are not normative. That is to say, a /// [`HasDisplayHandle`] implementor is completely allowed to return something /// unexpected. (For example, it's legal for someone to return a /// [`RawDisplayHandle::Xlib`] on macOS, it would just be weird, and probably /// requires something like XQuartz be used). #[non_exhaustive] #[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)] pubenum RawDisplayHandle { /// A raw display handle for UIKit (Apple's non-macOS windowing library). /// /// ## Availability Hints /// This variant is likely to be used on iOS, tvOS, (in theory) watchOS, and /// Mac Catalyst (`$arch-apple-ios-macabi` targets, which can notably use /// UIKit *or* AppKit), as these are the targets that (currently) support /// UIKit.
UiKit(UiKitDisplayHandle), /// A raw display handle for AppKit. /// /// ## Availability Hints /// This variant is likely to be used on macOS, although Mac Catalyst /// (`$arch-apple-ios-macabi` targets, which can notably use UIKit *or* /// AppKit) can also use it despite being `target_os = "ios"`.
AppKit(AppKitDisplayHandle), /// A raw display handle for the Redox operating system. /// /// ## Availability Hints /// This variant is used by the Orbital Windowing System in the Redox /// operating system.
Orbital(OrbitalDisplayHandle), /// A raw display handle for Xlib. /// /// ## Availability Hints /// This variant is likely to show up anywhere someone manages to get X11 /// working that Xlib can be built for, which is to say, most (but not all) /// Unix systems.
Xlib(XlibDisplayHandle), /// A raw display handle for Xcb. /// /// ## Availability Hints /// This variant is likely to show up anywhere someone manages to get X11 /// working that XCB can be built for, which is to say, most (but not all) /// Unix systems.
Xcb(XcbDisplayHandle), /// A raw display handle for Wayland. /// /// ## Availability Hints /// This variant should be expected anywhere Wayland works, which is /// currently some subset of unix systems.
Wayland(WaylandDisplayHandle), /// A raw display handle for the Linux Kernel Mode Set/Direct Rendering Manager /// /// ## Availability Hints /// This variant is used on Linux when neither X nor Wayland are available
Drm(DrmDisplayHandle), /// A raw display handle for the Linux Generic Buffer Manager. /// /// ## Availability Hints /// This variant is present regardless of windowing backend and likely to be used with /// EGL_MESA_platform_gbm or EGL_KHR_platform_gbm.
Gbm(GbmDisplayHandle), /// A raw display handle for Win32. /// /// ## Availability Hints /// This variant is used on Windows systems.
Windows(WindowsDisplayHandle), /// A raw display handle for the Web. /// /// ## Availability Hints /// This variant is used on Wasm or asm.js targets when targeting the Web/HTML5.
Web(WebDisplayHandle), /// A raw display handle for Android NDK. /// /// ## Availability Hints /// This variant is used on Android targets.
Android(AndroidDisplayHandle), /// A raw display handle for Haiku. /// /// ## Availability Hints /// This variant is used on HaikuOS.
Haiku(HaikuDisplayHandle),
}
/// An error that can occur while fetching a display or window handle. #[derive(Debug, Clone)] #[non_exhaustive] pubenum HandleError { /// The underlying handle cannot be represented using the types in this crate. /// /// This may be returned if the underlying window system does not support any of the /// representative C window handles in this crate. For instance, if you were using a pure Rust /// library to set up X11 (like [`x11rb`]), you would not be able to use any of the /// [`RawWindowHandle`] variants, as they all represent C types. /// /// Another example would be a system that isn't supported by `raw-window-handle` yet, /// like some game consoles. /// /// In the event that this error is returned, you should try to use the underlying window /// system's native API to get the handle you need. /// /// [`x11rb`]: https://crates.io/crates/x11rb
NotSupported,
/// The underlying handle is not available. /// /// In some cases the underlying window handle may become temporarily unusable. For example, on /// Android, the native window pointer can arbitrarily be replaced or removed by the system. In /// this case, returning a window handle would be disingenuous, as it would not be usable. A /// similar situation can occur on Wayland for the layer shell windows. /// /// In the event that this error is returned, you should wait until the handle becomes available /// again.
Unavailable,
}
impl fmt::Display for HandleError { fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result { matchself { Self::NotSupported => write!(
f, "the underlying handle cannot be represented using the types in this crate"
), Self::Unavailable => write!(f, "the underlying handle is not available"),
}
}
}
#[cfg(feature = "std")] impl std::error::Error for HandleError {}
¤ Diese beiden folgenden Angebotsgruppen bietet das Unternehmen0.20Angebot
(Wie Sie bei der Firma Beratungs- und Dienstleistungen beauftragen können 2026-06-18)
¤
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.