Please nominate your Qt Champions for 2021! https://forum.qt.io/topic/132134/looking-for-the-2021-qt-champions
macOS QPlainTextEdit accented characters blocking text selection
If a QPlainTextEdit is used on macOS Mojave and a accented character is typed then QPlainTextEdit blocks user actions like text selection. This behaviour occurs when the accent character is pressed and a user tries to select text, like he wants to abort the writing of a composed character. With Qt 5.11.2, 5.11.3 and 5.12.0 the QPlainTextEdit blocks text selection if the first half of a composed character is written.
Steps to reproduce the issue
- Make sure you have a German or French keyboard layout configured
- Write some random text, like "asdfkasklfhkashgkg"
- Go to a new line
´, like you would type
- Do not press
- Try to select the random text with the mouse
Result: The text selection on macOS is not possible, but on Windows 10 it works. Other apps like RStudio or the native TextEdit on macOS Mojave don't seam to have that issue.
Example project: https://github.com/MrMontag/macos-de-keyboard
Is this behaviour a feature or a bug? Do you know if there is a solution to this problem on macOS?
Hi and welcome to devnet,
Pretty good question... Did you already check the bug report system to see if there's something related ?
Yes, but I could not find bug report related to the issue.
I did a test on Ubuntu 18.04 LTS and the QPlainTextEdit behaves like expected, i.e. the text selection is possible. Furthermore, if you type a
´and relocate the cursor to a different line and enter
ágets inserted at the cursor position. This behaviour is consistent on Ubuntu and Windows. On macOS this is not possible because of the locked QPlainTextEdit. Looks like this is a bug on macOS...
Then please open a new report providing your example as a zip file and the instructions you posted here. Don't use links as they might disappear in the long run. Also, it's easier for the developer to have only one place to look for all the data.
The related ticket is https://bugreports.qt.io/browse/QTBUG-72707