diff options
author | Joel Challis <[email protected]> | 2025-01-08 03:12:54 +0000 |
---|---|---|
committer | GitHub <[email protected]> | 2025-01-07 19:12:54 -0800 |
commit | 6facb7a079740f975c41c9ae8d95f0735097933e (patch) | |
tree | 56754c717b484d78b43ffefaea8796973b38ca12 | |
parent | bcee1d2f2e17f85f75d67e32c809ae76bd3803ef (diff) | |
download | qmk_firmware-6facb7a079740f975c41c9ae8d95f0735097933e.tar.gz qmk_firmware-6facb7a079740f975c41c9ae8d95f0735097933e.zip |
Convert stray legacy warn/info docs panels (#24799)
-rw-r--r-- | docs/feature_macros.md | 4 | ||||
-rw-r--r-- | docs/feature_userspace.md | 5 | ||||
-rw-r--r-- | docs/features/mouse_keys.md | 4 |
3 files changed, 9 insertions, 4 deletions
diff --git a/docs/feature_macros.md b/docs/feature_macros.md index b4e37a1ba9..404eb4b38d 100644 --- a/docs/feature_macros.md +++ b/docs/feature_macros.md @@ -117,7 +117,9 @@ If yes, we send the string `"QMK is the best thing ever!"` to the computer via t We 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). Finally, we define the keymap so that the first button activates our macro and the second button is just an escape button. -?>It is recommended to use the SAFE_RANGE macro as per [Customizing Functionality](custom_quantum_functions). +::: tip +It is recommended to use the SAFE_RANGE macro as per [Customizing Functionality](custom_quantum_functions). +::: You might want to add more than one macro. You can do that by adding another keycode and adding another case to the switch statement, like so: diff --git a/docs/feature_userspace.md b/docs/feature_userspace.md index 1e7c3b37cd..d19b86cb46 100644 --- a/docs/feature_userspace.md +++ b/docs/feature_userspace.md @@ -74,8 +74,9 @@ Additionally, `config.h` here will be processed like the same file in your keyma The 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. -!>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) - +::: warning +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) +::: ## Readme (`readme.md`) diff --git a/docs/features/mouse_keys.md b/docs/features/mouse_keys.md index d755084f8e..86b50fa9c8 100644 --- a/docs/features/mouse_keys.md +++ b/docs/features/mouse_keys.md @@ -214,7 +214,9 @@ When additional overlapping mouse key is pressed, the mouse cursor will continue |`MOUSEKEY_OVERLAP_WHEEL_DELTA`|`MOUSEKEY_WHEEL_DELTA`|Step size of reset mouse wheel acceleration | |`MOUSEKEY_OVERLAP_INTERVAL` |`MOUSEKEY_INTERVAL` |Reset time between cursor movements in milliseconds (Kinetic mode only)| -?> This feature will not be applied on Inertial mode +::: tip +This feature will not be applied on Inertial mode +::: ## Use with PS/2 Mouse and Pointing Device |