Skip to content

slint crate: Expose parts of the winit backend's previously private API #8315

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

Merged
merged 8 commits into from
May 2, 2025

Conversation

tronical
Copy link
Member

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.

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.
@tronical tronical merged commit 0002df2 into master May 2, 2025
38 checks passed
@tronical tronical deleted the simon/winit-mod branch May 2, 2025 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants