-
Notifications
You must be signed in to change notification settings - Fork 909
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
Winit version 0.28.0 #2634
Winit version 0.28.0 #2634
Conversation
#2605 is the most important of those for us at Bevy :) |
#2636 is blocking an egui PR for maximizing windows, would love to see that in if possible (: |
@rib we have no breaking changes planned anymore for (EDIT: And if not, we should do a nonbreaking patch release for the recent contributions, i.e. to reduce |
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.
I think we should go for the new release now, all the requested changes have been made (or I've written a description on them as to why we'll delay with it).
The option as alt PR is still up, and I'll try to finish it today... The |
Right, no breaking changes planned currently. Doing a release for the logging cleanup should be fine. It'll also propagate the new url for the repo. |
I had a few winit Android issues I started looking at and had wanted to make more progress with (ime + surface_size) but it's fine if those things slip to the next release. For Android I've been looking more at issues in the JNI crate recently since I want to use it in the Android backend for Winit and but it has had a bunch of ergonomic and safety issues that I think need addressing first - so I've been a bit distracted from winit and android-activity. |
I've tested latest |
I'll schedule release for today's evening (UTC+3). If no-one has anything else to add I'd push a release. |
Winit #[cfg(any(
target_os = "linux",
target_os = "dragonfly",
target_os = "freebsd",
target_os = "netbsd",
target_os = "openbsd"
))]
{
use winit::platform::unix::EventLoopWindowTargetExtUnix;
if elwt.is_wayland() {
// Wayland-specific code here
}
} Now one needs to read the No action needed; better docs may be possible. |
nah, will wait for #2665... |
@kchibisov thanks for releasing! Can you now clean up some of the branch inconsistencies? There's a @madsmtm somehow strangely we seem to have some feature resolver problems on Rust 1.59 getting to |
@MarijnS95 msrv is 1.60 not 1.59 for the new winit. |
I'll try to look into that, but not sure if I can change much. |
@kchibisov right, silly of me to expect |
Patches that left
Some of the patches that might be worth merging for
0.28.0
:Window::is_minimized
#2626Rework DnD #2615Will take more design work, so let's not block on this oneWindowBuilder::with_active
#2585 (awaits macOS)If I've missed something or you want some bug to be fixed for
v0.28.0
let me know.Be aware that the next major release after the
0.28.0
(0.29.0
) will contain the new Wayland backend (updated to new wayland-rs) and likely new X11 backend(mixture of Xlib + Xcb, instead of raw xlib).--
CC of some main downstream consumers(if you're not interested in getting notified about release planning in winit let me know, so I won't even CC you again).
bevy
: @alice-i-cecile, @cartegui
/eframe
: @emilkiced
: @hecrjggez
: @PSteinhaustauri
: @amrbashirnannou
: @mitchmindtreeIf you have some issues with winit that you want fixed for 0.28.0 let me know while we're in release preparation stage, so I include them and try to look into.
Also would you prefer if winit had
rc
period or you're fine with the current policy withpatch
fixes right away, given that winit don't really have breaking changes. Initiallywe decided to not do
rc
releases, since it's easier to iterate and propagate the update without them, given that majority unlikely to use them and it's better to know that something broke if you push the update.