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
Support is_x11 and is_wayland on EventLoop #3672
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EventLoop
is not Active
it should have its own extensions.
New traits then (a copy of these other than the name)? |
Yes. Which is unfortunate, but it will prevent errors if someone tries to add API for the |
src/changelog/unreleased.md
Outdated
@@ -12,6 +12,7 @@ on how to add them: | |||
### Added | |||
|
|||
- Add `Window::turbo()`, implemented on X11, Wayland, and Web. | |||
- Implement `ActiveEventLoopExtWayland` and `ActiveEventLoopExtX11` for `EventLoop`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not correct anymore. It should mention the new traits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
changelog
module if knowledge of this change could be valuable to usersWinit v0.30 does not allow testing
is_wayland
on anEventLoop
(but only on anActiveEventLoop
), though this appears to be possible. This is an issue for me.The trait names
ActiveEventLoopExtWayland
andActiveEventLoopExtX11
are now inaccurate (may cause issues with future additional functionality?), but this is the most straightforward solution.Fixes #3670