You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #10702, ReceivedCharacter now contains SmolStr, which is a bit confusing. Is it a character or multiple characters?
The winit docs for the underlying winit event that populates this have some info about why it is not a char and what else might be in there. (but surely this isn't a str just for stray deadkeys, right? we should look into what locales or settings or whatever would produce multiple chars.)
ReceivedCharacter is also not consistent cross-platform in other important ways. See rust-windowing/winit#3381.
We might also want to point users to an alternative: KeyEvent::logical_key which is more consistent across platforms and is in a unified event stream with other keyboard events, which is important if you are developing a text input.
The text was updated successfully, but these errors were encountered:
How can Bevy's documentation be improved?
Since #10702,
ReceivedCharacter
now containsSmolStr
, which is a bit confusing. Is it a character or multiple characters?The winit docs for the underlying winit event that populates this have some info about why it is not a
char
and what else might be in there. (but surely this isn't astr
just for stray deadkeys, right? we should look into what locales or settings or whatever would produce multiplechars
.)ReceivedCharacter
is also not consistent cross-platform in other important ways. See rust-windowing/winit#3381.We might also want to point users to an alternative:
KeyEvent::logical_key
which is more consistent across platforms and is in a unified event stream with other keyboard events, which is important if you are developing a text input.The text was updated successfully, but these errors were encountered: