@aeva@mastodon.gamedev.place are you using KDE plasma for your machine for Mollytime?
-
@aeva@mastodon.gamedev.place are you using KDE plasma for your machine for Mollytime? Is there any annoying behavior with the touchscreen that you might want resolved or are willing to complain to me about?
-
@aeva@mastodon.gamedev.place are you using KDE plasma for your machine for Mollytime? Is there any annoying behavior with the touchscreen that you might want resolved or are willing to complain to me about?
@aud Wayland KDE has a hard coded gesture event that nearly always fires where if you press three fingers or more to a touch screen at once, it sends a touch cancel event to the application that tells it all active touch events are now invalid. This prevents mollytime from functioning correctly, and as a result I switched to another desktop environment. I do not know if this behavior is also present in X11 KDE.
-
@aud Wayland KDE has a hard coded gesture event that nearly always fires where if you press three fingers or more to a touch screen at once, it sends a touch cancel event to the application that tells it all active touch events are now invalid. This prevents mollytime from functioning correctly, and as a result I switched to another desktop environment. I do not know if this behavior is also present in X11 KDE.
@aud this is the bug I filed for it: https://bugs.kde.org/show_bug.cgi?id=510513
it got unceremoniously marked as a duplicate of https://bugs.kde.org/show_bug.cgi?id=402857, which is a decision I disagree with, but I did not feel like arguing as it seemed like there was a complete lack of urgency towards touch screen support in general and pretending otherwise would be a waste of my time and theirs.
-
@aud this is the bug I filed for it: https://bugs.kde.org/show_bug.cgi?id=510513
it got unceremoniously marked as a duplicate of https://bugs.kde.org/show_bug.cgi?id=402857, which is a decision I disagree with, but I did not feel like arguing as it seemed like there was a complete lack of urgency towards touch screen support in general and pretending otherwise would be a waste of my time and theirs.
@aud the touch cancel event allegedly (someone told me this on here, I don't have a source for it) is a contrivance of the automotive industry, where the singular purpose of a touch screen is to allow for simple control over the basic functions of a car so they can slash costs. A careless implementation of this protocol (KDE, gnome, and wayland compositors) results in a touch multi-touch screen that effectively cannot be used anything more than that.
-
@aud the touch cancel event allegedly (someone told me this on here, I don't have a source for it) is a contrivance of the automotive industry, where the singular purpose of a touch screen is to allow for simple control over the basic functions of a car so they can slash costs. A careless implementation of this protocol (KDE, gnome, and wayland compositors) results in a touch multi-touch screen that effectively cannot be used anything more than that.
@aud thus, if you have a, say, 10 point multitouch monitor, you can't just go and make a piano out of it, because 1) the automotive industry did not design a touch protocol that supports playing chords and frankly it would be irresponsible if they did, and 2) to date as far as I can tell not a single wayland developer has stopped to consider that this effectively shackles linux touch screen interfaces to the poverty of imagination that is the automotive industry
-
@aud thus, if you have a, say, 10 point multitouch monitor, you can't just go and make a piano out of it, because 1) the automotive industry did not design a touch protocol that supports playing chords and frankly it would be irresponsible if they did, and 2) to date as far as I can tell not a single wayland developer has stopped to consider that this effectively shackles linux touch screen interfaces to the poverty of imagination that is the automotive industry
@aud god forbid I want to use all ten fingers I paid real american dollars for