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
If I design keyboard shortcuts for quick access to specific inputs in my GUI, like: Ctrl+N to jump to some given text field, and one <TextInput> currently has the focus, it will use up and display the n letter (although key.ctrl === true, and my other useInput in the app will be invoked and will correctly pass the focus to where I wish, but... too late).
I would suggest an additional prop to <TextInput>: a keyFilter callback, which would receive the input+key (just as useInput) and would return true if the program should absorb (swallow) that key combination, or let it go through to the regular treatment of TextInput.
I can make a PR if someone else thinks this should exit.
Thanks
The text was updated successfully, but these errors were encountered:
If I design keyboard shortcuts for quick access to specific inputs in my GUI, like: Ctrl+N to jump to some given text field, and one
<TextInput>
currently has the focus, it will use up and display then
letter (althoughkey.ctrl === true
, and my otheruseInput
in the app will be invoked and will correctly pass the focus to where I wish, but... too late).I would suggest an additional prop to
<TextInput>
: akeyFilter
callback, which would receive the input+key (just asuseInput
) and would return true if the program should absorb (swallow) that key combination, or let it go through to the regular treatment ofTextInput
.I can make a PR if someone else thinks this should exit.
Thanks
The text was updated successfully, but these errors were encountered: