diff options
| author | Joel Challis <git@zvecr.com> | 2023-02-11 03:47:17 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-11 03:47:17 +0000 |
| commit | 11d49d00e74618500e5c51e4c7f858eb906ccea8 (patch) | |
| tree | ee827f3ed92a56861f6f5bf1d5f33d6068458d2c /users | |
| parent | 99918945149f98cf73f9365b0ad49a2fc07d1152 (diff) | |
Remove matrix_init_quantum/matrix_scan_quantum (#19806)
Diffstat (limited to 'users')
| -rw-r--r-- | users/drashna/callbacks.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/users/drashna/callbacks.md b/users/drashna/callbacks.md index 5908a66142..e23f7f6d86 100644 --- a/users/drashna/callbacks.md +++ b/users/drashna/callbacks.md @@ -2,7 +2,7 @@ Specifically QMK works by using customized callback functions for everything. This allows for multiple levels of customization. -`matrix_scan` calls `matrix_scan_quantum`, which calls `matrix_scan_kb`, which calls `matrix_scan_user`. +`matrix_scan` calls `matrix_scan_kb`, which calls `matrix_scan_user`. `process_record` calls a bunch of stuff, but eventually calls `process_record_kb` which calls `process_record_user` The same goes for `matrix_init`, `layer_state_set`, `led_set`, and a few other functions. |