summaryrefslogtreecommitdiff
path: root/basic/source/classes/codecompletecache.cxx
diff options
context:
space:
mode:
authorJan-Marek Glogowski <glogow@fbihome.de>2020-11-22 14:53:14 +0100
committerJan-Marek Glogowski <glogow@fbihome.de>2020-11-22 17:01:07 +0100
commit9d96088c2832b681ae079b29cbc977231674ad52 (patch)
treeabc3e36bca76c0b8515fe46bfabf0dbaf2260be4 /basic/source/classes/codecompletecache.cxx
parent62f8449f5f4a34654f742314e467202a0ff91a92 (diff)
Qt5 report input method language
This is in the spirit of tdf#108151, based on the information Qt provides for the IM setting. I don't know how correct it is, especially looking at Caolans comment 3 in that bug report regarding the assumed validity of GtkIMContextInfo. OTOH it seems to work well enough for my simple tests. Some BG info: while the QInputMethod object is a global one, it's "bound" to the focused window. So you'll get change events, when you change the input window, with the correct IM settings for the new one, be it a real window or just the menu bar. To prevent unneeded flushes of buffers and language lookup, this caches the current IM language of a window. The language is not affected just by changing keyboard mappings, which the bug reporter requested! It just works with a configured input method, like fcitx or ibus (which can have keyboard mappings too, which work correctly). Change-Id: Ia9133edf4d1ce77d29adbfe57c180db15db0a560 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/106354 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
Diffstat (limited to 'basic/source/classes/codecompletecache.cxx')
0 files changed, 0 insertions, 0 deletions