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
We make two changes to the keyboard enhancement API for usability:
If keyboard enhancements are not supported the KeyboardEnhancementsMsg should still be sent through update via a reasonable but short timeout. The user can detect whether features are supported with the existing methods like KeyboardEnhancementsMsg.SupportsKeyReleases().
The EnableKeyboardEnhancements command should be renamed to RequestKeyboardEnhancements.
The text was updated successfully, but these errors were encountered:
…sted and active enhancements (#1286)
refactor: keyboard: expose type and track requested and active
enhancements
This change exposes the `KeyboardEnhancements` type and tracks requested
and active enhancements in the `Program` struct. This change also
renames the `KeyboardEnhancement` type to `KeyboardEnhancementOption`
as well as`EnableKeyboardEnhancements` to `RequestKeyboardEnhancements`.
Fixes: #1283
We make two changes to the keyboard enhancement API for usability:
KeyboardEnhancementsMsg
should still be sent through update via a reasonable but short timeout. The user can detect whether features are supported with the existing methods likeKeyboardEnhancementsMsg.SupportsKeyReleases()
.EnableKeyboardEnhancements
command should be renamed toRequestKeyboardEnhancements
.The text was updated successfully, but these errors were encountered: