slint/internal/backends/selector
Simon Hausmann 0002df2520
slint crate: Expose parts of the winit backend's previously private API (#8315)
Similar to the wgpu access, the `unstable-winit-030` feature exposes a
`slint::winit_030` module, which in turn re-exports `winit` but also
provides access to the `WinitWindowAccessor` trait. The
`BackendSelector` is extended to provide a way to hook into window
attribute creation as well as providing a custom event loop builder,
similar to what `i_slint_backend_winit::BackendBuilder` provides.
2025-05-02 09:21:13 +02:00
..
LICENSES Simplify commercial license (#3063) 2024-05-31 14:06:17 +02:00
api.rs slint crate: Expose parts of the winit backend's previously private API (#8315) 2025-05-02 09:21:13 +02:00
build.rs Simplify commercial license (#3063) 2024-05-31 14:06:17 +02:00
Cargo.toml slint crate: Expose parts of the winit backend's previously private API (#8315) 2025-05-02 09:21:13 +02:00
lib.rs Fix clippy issues, plus a few manual cleanups 2025-02-06 17:28:51 +01:00
README.md Simplify commercial license (#3063) 2024-05-31 14:06:17 +02:00

NOTE: This library is an internal crate of the Slint project. This crate should not be used directly by applications using Slint. You should use the slint crate instead.

WARNING: This crate does not follow the semver convention for versioning and can only be used with version = "=x.y.z" in Cargo.toml.

The purpose of this crate is to select the default backend for Slint

The backend can either be a runtime or a build time decision. The runtime decision is decided by the SLINT_BACKEND environment variable. The built time default depends on the platform. In order for the crate to be available at runtime, they need to be added as feature