Quote:
Originally Posted by jugaor
A non-binding question: will this also apply to Ctrl+cursor movement/selection? (not a vital issue.)
|
No unfortunately not. Using ctrl+cursor move with an arrow key, still uses Qt QPlainTextEdit's internal approach to finding word breaks which we now know is broken.
I could "workaround" the separate double click event in CodeView because there is a specific double-click event handler that I could hijack to override their choice in a safe manner.
I can look to see if there is a way to override an arrow key press event but that is going to impact all uses of arrow keys, which is probably not want anyone wants and key press events need to be handled efficiently to prevent typing slowdowns.
The best approach is for you (or someone else who has this issue) to open a QtBug directly with Qt, and point out the inconsistencies in both approaches across multiple languages so that they will fix the word break iterator used by their QTextCursor routine to be unicode aware and not just a list of ascii quote and punctuation characters. You could even point them to this thread in Mobileread post for additional details.
Hope this helps.