User Details
- User Since
- Jul 7 2019, 6:22 AM (246 w, 4 d)
- Availability
- Available
May 16 2020
It seems that Qt devs finally showed interest in this problem. See QTBUG-84179
Aug 21 2019
MouseArea.pressAndHold runs based on the synthesised left press event, I don't see anything in your code which would prevent a conflict there.
Same for any widget code that uses a current QTapAndHoldGesture
No, we need exactly right click events. They are too important for many apps. For instance, how will we mark the cells in KMines without right click event? I backported my patch on 5.12 in order to replace native Qt version under Kubuntu and now I can successfully mark and unmark the cells.
Aug 19 2019
I made a patch which adds ability to emulate right click for Qt widgets which do not accepted touch events, but Qt devs say "such a feature should live in the platform itself (not in Qt), e.g. at the driver level or similar". So we have a strange situation when libinput (driver devs) have no plans to add right-click emulation to libinput, because it is the wrong layer of the stack and KWin devs think so, but Qt devs believe that it shall by done somewhere on this layer.
Aug 18 2019
Aug 14 2019
Aug 7 2019
Ping?
Jul 29 2019
Jul 28 2019
@elvisangelaccio, you have forgotten or I did not say clear enough that it is the previous cosmetic cosmetic version(Diff 61904) that was correct! Read my remark again in the revision conversation, please. @hein did not respond and I cannot say even if this one is fully correct for Korean. The one line solution does groupping of some Cyrillic symbols, which cannot be grouped toggether(aleast in Russian dictionary)
This was my fall. Sorry again for it.
Jul 27 2019
Ping!
Jul 21 2019
Friendly ping!
Jul 18 2019
I am sorry. I was so happy with this simple solution that forgot about one impornat aspect which is different from from language to language. If in a German dictionary 'O' and 'Ö' would be in the same group, in Russian 'Е' and 'Ё' or 'И' and 'Й' can never be together like new patch does. Probably, it is applicable to Korean, but in doesen't solve problem for all languages.
I used @hein idea to apply normalization which is implemented in unicode. Now it seems to be the final solution without working with particular writing system individually.
Jul 17 2019
Fixed brackets and spaces style
Jul 16 2019
Jul 15 2019
Equivalent solution
Jul 12 2019
Added braces
Jul 11 2019
I've deleted the else repeating and added warning about founded wrong behavior for Z group corner case.
Solving this requires another method for separation Latin and non Latin characters.
Jul 10 2019
Jul 8 2019
By the way. Even now it is broken for corner cases and I can't see any simple solution for this.