| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| skip_animated_cursor_test.diff | skip tst_seatv4::animatedCursor that fails in Debian | Dmitry Shachnev <mitya57@debian.org> | not-needed | upstream | 2020-04-30 | |
| fix_dead_keys.diff | allow QWaylandInputContext to accept composed key combinations At the moment, we are forcing user to choose to either compose or use the text-input channel. This patch brings some of the QComposeInputContext functionality in order to let applications understand dead key combinations like they are supposed to. . Having it in QWaylandInputContext rather than in QWaylandInputDevice should solve the problems 3aedd01271dc4f4a13103d632df224971ab2b6df had with 57c4af2b18c0fb1d266b245a107fa6cb876b9d9e, because we are doing it in the input context rather than before. This way, if the user is overriding the input method (e.g. by setting QT_IM_MODULE), all the key strokes will still be properly forwarded to the module to use. . This in turn allows us to solve https://bugs.kde.org/show_bug.cgi?id=411729 and https://bugs.kde.org/show_bug.cgi?id=405388 since we don't need to choose anymore between physical and virual keyboards anymore. |
no | upstream, https://code.qt.io/cgit/qt/qtwayland.git/commit/?id=cca1b94190a094b5 | 2021-06-27 |