705665957b
The normal flow for a keyDown event when sent to a text input enabled view (NSTextInputClient), is that it's sent through interpretKeyEvents, which in turn goes through the input methods, and result in either composing (marking) text, inserting text, or executing a text editing command such as moving the cursor to the beginning of the line. https://apple.co/3qDhwNb In our case, we prefer to treat "simple" text insertion (non-composed text) outside of the Qt input method protocol, and send these as normal key events instead. The same applies when a key event results in a text editing command that we don't handle. The problem is that in the latter case, the key event would contain the text that resulted from e.g. ⌘+K, or one of the function or arrow keys, which in many cases would not be suitable for inserting into a text field by a naive client that trusted the text property of the QKeyEvent. To work around this two exceptions were added; first in |
||
---|---|---|
.github/workflows | ||
bin | ||
cmake | ||
coin | ||
config.tests | ||
dist | ||
doc | ||
examples | ||
lib | ||
libexec | ||
LICENSES | ||
mkspecs | ||
qmake | ||
src | ||
tests | ||
util | ||
.cmake.conf | ||
.gitattributes | ||
.gitignore | ||
.lgtm.yml | ||
.tag | ||
CMakeLists.txt | ||
conanfile.py | ||
config_help.txt | ||
configure | ||
configure.bat | ||
configure.cmake | ||
dependencies.yaml | ||
qt_cmdline.cmake | ||
sync.profile |