From da82971f526f29dfb1029c5f438a2a46e61a4f7f Mon Sep 17 00:00:00 2001 From: Kirill Chibisov Date: Fri, 5 Jan 2024 12:42:27 +0400 Subject: [PATCH] Winit version 0.29.9 --- CHANGELOG.md | 2 ++ Cargo.toml | 2 +- README.md | 4 ++-- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f1da5bfb4..282132388 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,8 @@ Unreleased` header. # Unreleased +# 0.29.9 + - On X11, fix `NotSupported` error not propagated when creating event loop. - On Wayland, fix resize not issued when scale changes - On X11 and Wayland, fix arrow up on keypad reported as `ArrowLeft`. diff --git a/Cargo.toml b/Cargo.toml index 6b78a0e7b..10aee1149 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "winit" -version = "0.29.8" +version = "0.29.9" authors = ["The winit contributors", "Pierre Krieger "] description = "Cross-platform window creation library." edition = "2021" diff --git a/README.md b/README.md index e3fcb2ba2..0c9db39a4 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ ```toml [dependencies] -winit = "0.29.8" +winit = "0.29.9" ``` ## [Documentation](https://docs.rs/winit) @@ -156,7 +156,7 @@ For more details, refer to these `android-activity` [example applications](https If your application is currently based on `NativeActivity` via the `ndk-glue` crate and building with `cargo apk`, then the minimal changes would be: 1. Remove `ndk-glue` from your `Cargo.toml` -2. Enable the `"android-native-activity"` feature for Winit: `winit = { version = "0.29.8", features = [ "android-native-activity" ] }` +2. Enable the `"android-native-activity"` feature for Winit: `winit = { version = "0.29.9", features = [ "android-native-activity" ] }` 3. Add an `android_main` entrypoint (as above), instead of using the '`[ndk_glue::main]` proc macro from `ndk-macros` (optionally add a dependency on `android_logger` and initialize logging as above). 4. Pass a clone of the `AndroidApp` that your application receives to Winit when building your event loop (as shown above).