summaryrefslogtreecommitdiff
path: root/quantum
AgeCommit message (Collapse)Author
2022-08-30Use a macro to compute the size of arrays at compile time (#18044)Jeff Epler
* Add ARRAY_SIZE and CEILING utility macros * Apply a coccinelle patch to use ARRAY_SIZE * fix up some straggling items * Fix 'make test:secure' * Enhance ARRAY_SIZE macro to reject acting on pointers The previous definition would not produce a diagnostic for ``` int *p; size_t num_elem = ARRAY_SIZE(p) ``` but the new one will. * explicitly get definition of ARRAY_SIZE * Convert to ARRAY_SIZE when const is involved The following spatch finds additional instances where the array is const and the division is by the size of the type, not the size of the first element: ``` @ rule5a using "empty.iso" @ type T; const T[] E; @@ - (sizeof(E)/sizeof(T)) + ARRAY_SIZE(E) @ rule6a using "empty.iso" @ type T; const T[] E; @@ - sizeof(E)/sizeof(T) + ARRAY_SIZE(E) ``` * New instances of ARRAY_SIZE added since initial spatch run * Use `ARRAY_SIZE` in docs (found by grep) * Manually use ARRAY_SIZE hs_set is expected to be the same size as uint16_t, though it's made of two 8-bit integers * Just like char, sizeof(uint8_t) is guaranteed to be 1 This is at least true on any plausible system where qmk is actually used. Per my understanding it's universally true, assuming that uint8_t exists: https://stackoverflow.com/questions/48655310/can-i-assume-that-sizeofuint8-t-1 * Run qmk-format on core C files touched in this branch Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
2022-08-29[Core] Introduce pointing device specific debug messages (#17663)Stefan Kerkmann
2022-08-28Use `TAP_CODE_DELAY` for encoder mapping by default (#18098)Nick Brassel
2022-08-28Fix mouse report comparison failing on shared EP (#18060)Drzony
Co-authored-by: Dasky <32983009+daskygit@users.noreply.github.com>
2022-08-28Switch over MANUFACTURER and PRODUCT to string literals (#18183)Ryan
2022-08-27Clean-up of `#define _ADJUST 16` instances (#18182)James Young
* enum layer_names: 40percentclub/nori default keymap * enum layer_names: ergotravel default keymap * enum layer_names: handwired/atreus50 default keymap * enum layer_names: handwired/ortho5x13 default keymap * enum layer_names: keebio/levinson default keymap * enum layer_names: keebio/nyquist default keymap * enum layer_names: keebio/rorschach default keymap * enum layer_names: keebio/viterbi default keymap * enum layer_names: keebio/wavelet default keymap * enum layer_names: lets_split default keymap * enum layer_names: maple_computing/launchpad reference keymaps Update `default` and `default_rgb` keymaps. * enum layer_names: maple_computing/minidox default keymap * enum layer_names: miniaxe reference keymaps Update `default` and `underglow` keymaps. * enum layer_names: omkbd/ergodash/mini default keymap * enum layer_names: omkbd/ergodash/rev1 default keymap * enum layer_names: orthodox default keymap * enum layer_names: unikeyboard/divergetm2 default keymap * enum layer_names: woodkeys/scarletbandana default keymap * add _Static_assert to keymap_introspection.c
2022-08-27Add missing SS_LOPT and SS_ROPT defines (#18175)Joel Challis
2022-08-15Fix DV_SCLN and DV_COLN in keymap_spanish_dvorak.h (#18043)precondition
2022-08-15[Bug] Add key event check to `is_tap_record` and remove `is_tap_key` (#18063)Stefan Kerkmann
2022-08-14Remove duplicate COMBINING HORN in keymap_us_extended.h (#18045)precondition
2022-08-14Fix Caps Word to treat mod-taps more consistently. (#17463)Pascal Getreuer
* Fix Caps Word to treat mod-taps more consistently. Previously, holding any mod-tap key while Caps Word is active stops Caps Word, and this happens regardless of `caps_word_press_user()`. Yet for regular mod keys, AltGr (KC_RALT) is ignored, Shift keys are passed to `caps_word_press_user()` to determine whether to continue, and similarly, a key `RSFT(KC_RALT)` representing Right Shift + Alt is passed to `caps_word_press_user()` to determine whether to continue. This commit makes held mod-tap keys consistent with regular mod keys: * Holding a `RALT_T` mod-tap is ignored. * When holding a shift mod-tap key, `KC_LSFT` or `KC_RSFT` is passed to `caps_word_press_user()` to determine whether to continue. * When holding a Right Shift + Alt (`RSA_T`) mod-tap, `RSFT(KC_RALT)` is passed to `caps_word_press_user()`. Particularly, with this fix a user may choose to continue Caps Word when a shift mod-tap key is held by adding `KC_LSFT` and `KC_RSFT` cases in `caps_word_press_user()`. For instance as ``` bool caps_word_press_user(uint16_t keycode) { switch (keycode) { // Keycodes that continue Caps Word, with shift applied. case KC_A ... KC_Z: case KC_MINS: add_weak_mods(MOD_BIT(KC_LSFT)); // Apply shift to the next key. return true; // Keycodes that continue Caps Word, without shifting. case KC_1 ... KC_0: case KC_BSPC: case KC_DEL: case KC_UNDS: case KC_LSFT: // <<< Added here. case KC_RSFT: return true; default: return false; // Deactivate Caps Word. } } ``` * Fix Caps Word to treat mod-taps more consistently. Previously, holding any mod-tap key while Caps Word is active stops Caps Word, and this happens regardless of `caps_word_press_user()`. Yet for regular mod keys, AltGr (KC_RALT) is ignored, Shift keys are passed to `caps_word_press_user()` to determine whether to continue, and similarly, a key `RSFT(KC_RALT)` representing Right Shift + Alt is passed to `caps_word_press_user()` to determine whether to continue. This commit makes held mod-tap keys consistent with regular mod keys: * Holding a `RALT_T` mod-tap is ignored. * When holding a shift mod-tap key, `KC_LSFT` or `KC_RSFT` is passed to `caps_word_press_user()` to determine whether to continue. * When holding a Right Shift + Alt (`RSA_T`) mod-tap, `RSFT(KC_RALT)` is passed to `caps_word_press_user()`. Particularly, with this fix a user may choose to continue Caps Word when a shift mod-tap key is held by adding `KC_LSFT` and `KC_RSFT` cases in `caps_word_press_user()`. For instance as ``` bool caps_word_press_user(uint16_t keycode) { switch (keycode) { // Keycodes that continue Caps Word, with shift applied. case KC_A ... KC_Z: case KC_MINS: add_weak_mods(MOD_BIT(KC_LSFT)); // Apply shift to the next key. return true; // Keycodes that continue Caps Word, without shifting. case KC_1 ... KC_0: case KC_BSPC: case KC_DEL: case KC_UNDS: case KC_LSFT: // <<< Added here. case KC_RSFT: return true; default: return false; // Deactivate Caps Word. } } ``` * Update quantum/process_keycode/process_caps_word.c Co-authored-by: Joel Challis <git@zvecr.com>
2022-08-14Added emacs as an "operating system" for input mode. (#16949)Chewxy
2022-08-14Replace ; by : in the shifted symbols ASCII art of keymap_norman (#18029)precondition
Thanks!
2022-08-14Align TO() max layers with other keycodes (#17989)Joel Challis
2022-08-13Use ANSI ASCII art and fix comments for LT_COLN and LT_UNDS in ↵precondition
keymap_lithuanian_qwerty.h (#18028)
2022-08-13Fix LV_CCAR and LV_NCED (#18025)precondition
2022-08-13Fix Caps Word capitalization when used with Combos + Auto Shift. (#17549)Pascal Getreuer
2022-08-13Add led matrix support for CKLED2001 (#17643)lokher
2022-08-12KR_DQUO S(KR_COLN) → KR_DQUO S(KR_QUOT) (#18011)precondition
2022-08-12define CZ_PERC S(CZ_PLUS) → define CZ_PERC S(CZ_EQL) (#18008)precondition
2022-08-12Remove invisible variation selector-15 from keymap_japanese.h (#18007)precondition
2022-08-12Use LT_ZCAR in place of LT_PLUS for modded kc definitions (#18000)precondition
2022-08-12Fix Bépo's BP_NNBS (narrow non-breaking space) (#17999)precondition
Co-authored-by: Ryan <fauxpark@gmail.com>
2022-08-12Merge remote-tracking branch 'origin/master' into developQMK Bot
2022-08-12Remove legacy keycode use from command (#18002)Joel Challis
2022-08-11Refactor Pixel Fractal effect (#17602)Albert Y
* Refactor effect with smaller array * Add RGB_MATRIX_USE_LIMITS call * Remove spaces Co-authored-by: Drashna Jaelre <drashna@live.com> Co-authored-by: Drashna Jaelre <drashna@live.com>
2022-08-07Merge remote-tracking branch 'origin/master' into developQMK Bot
2022-08-07fix comment space code in quantum/matrix_common.c (#17942)Takeshi ISHII
2022-08-07Always run pointing device init (#17936)Drashna Jaelre
2022-08-06[Core] Process all changed keys in one scan loop, deprecate ↵Stefan Kerkmann
`QMK_KEYS_PER_SCAN` (#15292)
2022-08-06[Core] guard RPC invocation by checking RPC info against crc checksum (#17840)Stefan Kerkmann
2022-07-31Add ST7735 driver to Quantum Painter (#17848)David Hoelscher
2022-07-29Implement relative mode for Cirque trackpad (#17760)Drzony
2022-07-30Merge remote-tracking branch 'origin/master' into developQMK Bot
2022-07-30Fix check when compiling HID Joystick with digital driver (#17844)Drashna Jaelre
2022-07-28Rename postprocess_steno_user → post_process_steno_user (#17823)precondition
2022-07-26Constrain 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-26Avoid OOB in dynamic_keymap_reset (#17695)Joel Challis
2022-07-25Cirque circular scroll: Support POINTING_DEVICE_COMBINED (#17654)Daniel Kao
2022-07-25Fix QK_MAKE's reboot check (#17795)Drashna Jaelre
2022-07-23implement `tap_code16_delay` (#17748)JayceFayne
2022-07-23Add ability to enter bootloader mode from `QK_MAKE` (#17745)jack
2022-07-21Move Pointing Device Initialization (#17740)Drashna Jaelre
Move Pointing Device Initialization to after Split Post Initialization If both pointing device and split is enabled, the pointing device init needs to be called after the split post init, otherwise the connection (serial/etc) isn't initialized yet, and any commands that need to send data over (such as calling the set cpi command) never get sent over.
2022-07-21VIA Encoder Map Support (#17734)Wilba
2022-07-20fix syntax error (#17732)mknj
2022-07-20Move Pointing Device code to a subdirectory (#17684)Drashna Jaelre
2022-07-19Add support for PAW3204 Optical Sensor (#17669)Drashna Jaelre
Co-authored-by: gompa <gompa@h-bomb.nl> Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
2022-07-18 Allow dynamic keymap to compile without via.h (#17703)Joel Challis
2022-07-14Add LED limit call (#17679)Albert Y
2022-07-14Fix the use of LED limits (#17678)Albert Y