summaryrefslogtreecommitdiffstats
path: root/doc/src/snippets/code/src_script_qscriptvalue.cpp
diff options
context:
space:
mode:
authorSami Merila <sami.merila@nokia.com>2011-10-20 13:46:12 (GMT)
committerCasper van Donderen <casper.vandonderen@nokia.com>2011-10-21 10:15:59 (GMT)
commit65c5f90299193d1ef658b9b17cab551e03fbe14a (patch)
tree63691e65cce1d356b07f5568996af3be83c6d584 /doc/src/snippets/code/src_script_qscriptvalue.cpp
parent67dd642ca7cd7f61ba5de83218a3933ffe12f10e (diff)
downloadQt-65c5f90299193d1ef658b9b17cab551e03fbe14a.zip
Qt-65c5f90299193d1ef658b9b17cab551e03fbe14a.tar.gz
Qt-65c5f90299193d1ef658b9b17cab551e03fbe14a.tar.bz2
Accepting predicted text using hardware keyboard replaces unwanted part
Current implementation of Symbian input context assumes that predicted word replacement happens so that the original typed text is at the end of the surrounded text. The logic fails, if to-be-predicted text is in the middle of, or in the beginning of another, already accepted word. As a fix, input context need to store the original cursor position, when reset() was called (this happens when word selection list appears). Input context is already storing a copy of a preedit string in this situation. Then, when word replacement happens, this stored cursor position is used instead of current cursor position (the native side might temporarily move the cursor to the end when word selection list opens or closes) to replace the typed word with one selected from suggested word list. Stored cursor position is dismissed immediately after used, or if cached preedit string is dismissed. Task-number: QTBUG-22147 Reviewed-by: Miikka Heikkinen
Diffstat (limited to 'doc/src/snippets/code/src_script_qscriptvalue.cpp')
0 files changed, 0 insertions, 0 deletions