qmk_sweep_skeletyl/quantum/pointing_device/pointing_device.c, branch master

Add core handling for pointing device failures. (#25315)

2025-06-14T12:55:35+00:00

Add additional hooks for Community modules (#25050)

2025-05-05T00:21:47+00:00

High resolution scrolling (without feature report parsing) (#24423)

2025-04-22T22:04:31+00:00

* hires scrolling without feature report parsing * fix valid range for exponent * fix incorrect minimum exponent value documentation

[chore]: move and rename mouse/scroll min/max defines (#25141)

2025-04-13T16:36:13+00:00

* protocol: move {XY/HV}_REPORT_{MIN,MAX} into report.h ..to allow easier re-use in other code implementations. * protocol: rename {XY/HV}_REPORT_{MIN/MAX} to MOUSE_REPORT_{XY/HV}_{MIN/MAX} ..to avoid naming collisions.

Move pointing device driver code (#24445)

2024-10-25T17:11:51+00:00

Co-authored-by: Drashna Jaelre

Extended wheel reports (#24422)

2024-10-06T09:26:55+00:00

extended wheel reports

Normalise mouse keycodes (#23975)

2024-07-03T08:35:54+00:00

Fix pointing_device_set_cpi_on_side() (#23391)

2024-04-04T03:39:02+00:00

Co-authored-by: Less/Rikki <86894501+lesshonor@users.noreply.github.com>

Update GPIO macro usages in core (#23093)

2024-02-18T06:08:27+00:00

pointing_device: motion pin define and c-format weirdness (#22802)

2024-01-10T16:38:13+00:00

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