Closed SonnyX closed 3 years ago
It requires some adaptation in our code but yeah, it makes sense. Why did you close?
Because I first want to fix the build errors! :)
As far as I remember, they rearranged work with the events a bit and with the event loop. Nothing hard to rewrite.
Some stuff has been deprecated, however as it is, this builds. I recommend checking for yourself if the example still works properly however.
Oh, winit 0.19 contains backtrace crate that contains object crate that forces us to bump the MSRV. winit 0.20+, on the other hand, doesn't contain it.
@SonnyX I've reviewed this PR and decided to rewrite the example a bit differently, see 7062521. Well, the diff is quite ugly, but basically the rendering part was moved from the old WindowEvent::Refresh
to a new Event::RedrawRequested
, and the loop closure has been adapted to the new event loop model. Also, the keyboard modifiers are no longer a part of different events but rather are sent as a different event, see fdc7ba0.
Awesome, thanks for keeping the deps up to date :)
Updates the requirements on winit to permit the latest version.
Release notes
Sourced from winit's releases.
Changelog
Sourced from winit's changelog.
Commits
6db308f
Release 0.24.06f70fd9
Windows: Changed thread_event_target_callback's WM_DESTROY to WM_NCDESTROY (#...db038d9
On Windows, implement 'Window::set_ime_position' with IMM APIc5620ef
On Wayland, don't drop extra mouse buttons8fb7aa5
Android: Improved multi-touch (#1783)6ddee9a
Ability to force a theme on Windows (#1666)5700359
Android: support multi-touch (#1776)0861a35
Add 'request_user_attention' to Windowf79efec
Fix deprecation warning in the window icon example77d5d20
Windows: Delayed Message Boxes Fix. (#1769)