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
Current ReceivedImeText only pass the string when users use IME. While we could use key event to receive characters if they are not using IME, it will be a mess if we need to handle both inputs with and without IME.
I believe it's better to get an event that can pass the determined text from OS.
I think we should bring back the old keyboard api and stick with it for a while until winit finishes all of the stuff related to the new keyboard api .
Okay I read through winit's new keyboard api issue and turns out that they indeed removed ReceivedCharacter and replaced by KeyEvent.logical_key. more info
they also introduced ReceivedImeText but it is temporary and will be replaced with CompositionEvents but that is still an unfinished api so we use ReceivedImeText until it is finished.
Current
ReceivedImeText
only pass the string when users use IME. While we could use key event to receive characters if they are not using IME, it will be a mess if we need to handle both inputs with and without IME.I believe it's better to get an event that can pass the determined text from OS.
cc @lucasfernog and @amrbashir since this will change a bit on Tauri internally
The text was updated successfully, but these errors were encountered: