https://bugs.kde.org/show_bug.cgi?id=510591
--- Comment #19 from Maxim Kartashev <[email protected]> --- > ... > it means that there was a motion event but only with absolute coordinates > (the app could compute a delta value in such a case if it is okay). I'm afraid the specification does not support this approach. Here's a quote from https://wayland.app/protocols/relative-pointer-unstable-v1: "Relative motions are not coupled to wl_pointer.motion events, and can be sent in combination with such events, but also independently. There may also be scenarios where wl_pointer.motion is sent, but there is no relative motion" So even if KWin currently guarantees that a frame event will follow the motion and relative_motion events and they are always grouped together, who's to say that the order remains in future versions after some refactoring, etc? -- You are receiving this mail because: You are watching all bug changes.
