David Redondo cc4d99aea4 Fix button to Qt::MouseButton mapping ... Even though the names seem to match, QtWayland maps button values to enum values in ascendung order (as it does on X11). The wrong mapping is usually not a problem because we send the native button events to clients. However when the Qt names or values are used for communication between KWin and a client this leads to misunderstandings. BUG:465463 FIXED-IN:5.27.1		2023-02-10 09:27:37 +00:00
..
CMakeLists.txt
device_test.cpp
gesture_event_test.cpp	use std::chrono::microseconds for time in input events	2022-12-21 21:07:15 +01:00
input_event_test.cpp	use std::chrono::microseconds for time in input events	2022-12-21 21:07:15 +01:00
key_event_test.cpp	use std::chrono::microseconds for time in input events	2022-12-21 21:07:15 +01:00
mock_libinput.cpp	Fix button to Qt::MouseButton mapping	2023-02-10 09:27:37 +00:00
mock_libinput.h	use std::chrono::microseconds for time in input events	2022-12-21 21:07:15 +01:00
pointer_event_test.cpp	use std::chrono::microseconds for time in input events	2022-12-21 21:07:15 +01:00
switch_event_test.cpp	use std::chrono::microseconds for time in input events	2022-12-21 21:07:15 +01:00
touch_event_test.cpp	use std::chrono::microseconds for time in input events	2022-12-21 21:07:15 +01:00