···117117We return `true` to indicate to the caller that the key press we just processed should continue to be processed as normal (as we didn't replace or alter the functionality).
118118Finally, we define the keymap so that the first button activates our macro and the second button is just an escape button.
119119120120-?>It is recommended to use the SAFE_RANGE macro as per [Customizing Functionality](custom_quantum_functions).
120120+::: tip
121121+It is recommended to use the SAFE_RANGE macro as per [Customizing Functionality](custom_quantum_functions).
122122+:::
121123122124You might want to add more than one macro.
123125You can do that by adding another keycode and adding another case to the switch statement, like so:
+3-2
docs/feature_userspace.md
···74747575The reason for this, is that `<name>.h` won't be added in time to add settings (such as `#define TAPPING_TERM 100`), and including the `<name.h>` file in any `config.h` files will result in compile issues.
76767777-!>You should use the `config.h` for [configuration options](config_options), and the `<name>.h` file for user or keymap specific settings (such as the enum for layer or keycodes)
7878-7777+::: warning
7878+You should use the `config.h` for [configuration options](config_options), and the `<name>.h` file for user or keymap specific settings (such as the enum for layer or keycodes)
7979+:::
79808081## Readme (`readme.md`)
8182
+3-1
docs/features/mouse_keys.md
···214214|`MOUSEKEY_OVERLAP_WHEEL_DELTA`|`MOUSEKEY_WHEEL_DELTA`|Step size of reset mouse wheel acceleration |
215215|`MOUSEKEY_OVERLAP_INTERVAL` |`MOUSEKEY_INTERVAL` |Reset time between cursor movements in milliseconds (Kinetic mode only)|
216216217217-?> This feature will not be applied on Inertial mode
217217+::: tip
218218+This feature will not be applied on Inertial mode
219219+:::
218220219221## Use with PS/2 Mouse and Pointing Device
220222