E525 Winit version 0.30.13 by kchibisov · Pull Request #4498 · rust-windowing/winit · GitHub
[go: up one dir, main page]

Skip to content

Winit version 0.30.13#4498

Merged
kchibisov merged 10 commits intov0.30.xfrom
kchibisov/release-03013
Mar 2, 2026
Merged

Winit version 0.30.13#4498
kchibisov merged 10 commits intov0.30.xfrom
kchibisov/release-03013

Conversation

@kchibisov
Copy link
Member

No description provided.

Winit only supports text, thus we should ignore the rest
instead of crashing.
@kchibisov kchibisov force-pushed the kchibisov/release-03013 branch 3 times, most recently from b440e5d to a42e8a7 Compare March 1, 2026 14:22
itsamine27 and others added 6 commits March 1, 2026 23:26
The xfixes implementation is not that reliable and rather simple to
replace, so use x11rb to implement the same functionality.

Fixes #4120.
Co-authored-by: avitran0 <holyhades64@gmail.com>
macOS native Pinyin IME can send a selected_range that exceeds the
marked text string length (e.g. index 8 for a 6-character string).
This caused an NSRangeException in substringToIndex:, crashing the
application with SIGABRT.

Clamp both location and end to the string's UTF-16 length before
calling substringToIndex.
@kchibisov kchibisov force-pushed the kchibisov/release-03013 branch 4 times, most recently from c59ae7c to f64a342 Compare March 1, 2026 14:33
@madsmtm madsmtm added this to the Version 0.30.13 milestone Mar 1, 2026
@madsmtm madsmtm linked an issue Mar 1, 2026 that may be closed by this pull request
@MarijnS95
Copy link
Member

Looking at this, I thought I missed a PR after initially fixing something on "our" old 0.29 backport branch which we're still using... But turns out I never PR'd this: #4499

Would it make sense to backport it to 0.30 too? Might be useful.

The `text` field on `KeyEvent` was hardcoded to `None` on Android,
making it impossible for custom `NativeActivity` subclasses that
show the IME to receive functional text input using *for example* the
existing `winit-egui` crate which relies on this field being set.

Use `Key::to_text()` on press events to derive `text` from
`logical_key`, matching the convention used by the Windows and macOS
backends.

Supposedly that doesn't include all kinds of special virtual unicode
keys, but at least the basics work this way.
@kchibisov kchibisov force-pushed the kchibisov/release-03013 branch from f64a342 to 3d351ae Compare March 2, 2026 13:44
@kchibisov kchibisov merged commit e9809ef into v0.30.x Mar 2, 2026
47 of 53 checks passed
@kchibisov kchibisov deleted the kchibisov/release-03013 b 96DE ranch March 2, 2026 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Release 0.30.13?

10 participants

0