Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-11-20 | Azoteq IQS5xx support (#22280) | Dasky | |
2023-10-11 | add missing gpio include for pointing motion pin (#22246) | Dasky | |
2023-10-08 | Fix build error when Automatic Mouse Layer is enabled (#22229) | ikorihn | |
2023-07-16 | quantum: remove direct `quantum.h` includes (#21507) | Ryan | |
2023-05-06 | Make Pointing Device Auto Layer more configurable (#20061) | Drashna Jaelre | |
Co-authored-by: Pablo MartÃnez <58857054+elpekenin@users.noreply.github.com> | |||
2023-04-03 | Added PMW3320 driver (#19543) | Vladislav Marchenko | |
2023-03-30 | Add last activity functions for pointing device (#20079) | Drashna Jaelre | |
2022-11-09 | Fix jump in report value when scale changes during cirque get report (#18992) | Christopher Hoage | |
Fixes undefined | |||
2022-11-06 | Fix keycode parameter extraction to match the new DD keycodes (#18977) | Sergey Vlasov | |
* Add macros to extract parameters from keycode values Implement both encoding and decoding for keycodes like TO(layer) or LM(layer, mod) in one place, so that the decoding won't get out of sync with the encoding. While at it, fix some macros for creating keycode values that did not apply the appropriate masks to parameters (and therefore could allow the result to be out of range if a wrong parameter was passed). * keymap_common: Use extraction macros for keycodes * pointing_device_auto_mouse: Use extraction macros for keycodes Fixes #18970. * process_autocorrect: Use extraction macros for keycodes * process_caps_word: Use extraction macros for keycodes (Also fix a minor bug - SH_TG was not handled properly) * process_leader: Use extraction macros for keycodes (Technically the code is not 100% correct, because it always assumes that the LT() or MT() action was a tap, but it's a separate issue that already existed before the keycode changes.) * process_unicode: Use extraction macros for keycodes * process_unicodemap: Use extraction macros for keycodes | |||
2022-09-26 | Enabling Pointing Device support in register code functions (#18363) | Drashna Jaelre | |
2022-09-24 | Allow Active High for Pointing Device Motion Pin (#18404) | Thomas | |
Needed by the Cirque Trackpad for motion detection | |||
2022-09-24 | Format code according to conventions (#18466) | QMK Bot | |
2022-09-23 | [Core] Pointing Device Automatic Mouse Layer (#17962) | Alabastard-64 | |
Co-authored-by: Drashna Jaelre <drashna@live.com> Co-authored-by: Stefan Kerkmann <karlk90@pm.me> | |||
2022-09-14 | Fix cirque tap from secondary side (#18351) | Dasky | |
2022-08-29 | [Core] Introduce pointing device specific debug messages (#17663) | Stefan Kerkmann | |
2022-08-28 | Fix mouse report comparison failing on shared EP (#18060) | Drzony | |
Co-authored-by: Dasky <32983009+daskygit@users.noreply.github.com> | |||
2022-08-07 | Always run pointing device init (#17936) | Drashna Jaelre | |
2022-07-29 | Implement relative mode for Cirque trackpad (#17760) | Drzony | |
2022-07-26 | Constrain Cirque Pinnacle coordinates (#17803) | Daniel Kao | |
Static x & y should be the same type as touchData.xValue & touchData.yValue: uint16_t. Their delta could be larger than int8_t and should be constrained to mouse_xy_report_t. | |||
2022-07-25 | Cirque circular scroll: Support POINTING_DEVICE_COMBINED (#17654) | Daniel Kao | |
2022-07-20 | Move Pointing Device code to a subdirectory (#17684) | Drashna Jaelre | |