diff options
author | JohSchneider <[email protected]> | 2024-01-10 16:38:13 +0000 |
---|---|---|
committer | GitHub <[email protected]> | 2024-01-10 17:38:13 +0100 |
commit | d9b1ab9ae03a5d6ca09902a1c0d2927548829de8 (patch) | |
tree | f7fd8e4ed6b7a2d6f0b6b94ae5814a0fb31e4f60 /drivers/eeprom | |
parent | 41948350e866b8881a82a384342686942fc92865 (diff) | |
download | qmk_firmware-d9b1ab9ae03a5d6ca09902a1c0d2927548829de8.tar.gz qmk_firmware-d9b1ab9ae03a5d6ca09902a1c0d2927548829de8.zip |
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 <[email protected]>
Diffstat (limited to 'drivers/eeprom')
0 files changed, 0 insertions, 0 deletions