qmk_firmware/quantum/pointing_device
JohSchneider d9b1ab9ae0
pointing_device: motion pin define and c-format weirdness (#22802)
the mutual exclusive POINTING_DEVICE_MOTION_PIN and SPLIT_POINTING_ENABLE influence if and how the `pointing_device_driver.get_report` is triggered. now the way the define is wrapping around an "unbraced" if leads clang-format to weirdly indent the first line in the 'SPLIT_POINTING_ENABLE' as the first command after the if.

this hints that any code addition in between the two - that possibly should run regardless, would break the if-def enabled code.

this can be solved by adding a pair of curly braces in the POINTING_DEVICE_MOTION_PIN part, to clearly denote which commands are to be skipped if the motion pin shows now activity.

Co-authored-by: Johannes <you@example.com>
2024-01-10 17:38:13 +01:00
..
pointing_device.c pointing_device: motion pin define and c-format weirdness (#22802) 2024-01-10 17:38:13 +01:00
pointing_device.h Azoteq IQS5xx support (#22280) 2023-11-20 16:25:35 +00:00
pointing_device_auto_mouse.c Add option for auto mouse movement threshold (#21398) 2024-01-09 21:16:50 +11:00
pointing_device_auto_mouse.h Add option for auto mouse movement threshold (#21398) 2024-01-09 21:16:50 +11:00
pointing_device_drivers.c Azoteq IQS5xx support (#22280) 2023-11-20 16:25:35 +00:00
pointing_device_gestures.c
pointing_device_gestures.h