aboutsummaryrefslogtreecommitdiff
path: root/readme.md
diff options
context:
space:
mode:
authorWojciech Siewierski <wojciech.siewierski@onet.pl>2016-10-09 12:52:39 +0200
committerWojciech Siewierski <wojciech.siewierski@onet.pl>2016-10-09 12:52:39 +0200
commit70f32842e5d94f14d05c1f9adcb1b1144a25a132 (patch)
treebefd2c5ed38da2b730f5db75748e99d44ba2e812 /readme.md
parenta9df99b81c787862dc3fa11bd854fe39e704da81 (diff)
downloadqmk_firmware-70f32842e5d94f14d05c1f9adcb1b1144a25a132.tar.gz
qmk_firmware-70f32842e5d94f14d05c1f9adcb1b1144a25a132.zip
Reduce the default dynamic macro buffer
There have been reports of it leaving not enough free memory preventing the keyboard from working properly.
Diffstat (limited to 'readme.md')
-rw-r--r--readme.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/readme.md b/readme.md
index a7320202b..d28d7c3ff 100644
--- a/readme.md
+++ b/readme.md
@@ -823,7 +823,7 @@ And then, to assign this macro to a key on your keyboard layout, you just use `M
823 823
824## Dynamic macros: record and replay macros in runtime 824## Dynamic macros: record and replay macros in runtime
825 825
826In addition to the static macros described above, you may enable the dynamic macros which you may record while writing. They are forgotten as soon as the keyboard is unplugged. Only two such macros may be stored at the same time, with the total length of 128 keypresses. 826In addition to the static macros described above, you may enable the dynamic macros which you may record while writing. They are forgotten as soon as the keyboard is unplugged. Only two such macros may be stored at the same time, with the total length of 64 keypresses (by default).
827 827
828To enable them, first add a new element to the `planck_keycodes` enum -- `DYNAMIC_MACRO_RANGE`: 828To enable them, first add a new element to the `planck_keycodes` enum -- `DYNAMIC_MACRO_RANGE`:
829 829
@@ -864,7 +864,7 @@ Add the following code to the very beginning of your `process_record_user()` fun
864 864
865To start recording the macro, press either `DYN_REC_START1` or `DYN_REC_START2`. To finish the recording, press the `_DYN` layer button. The handler awaits specifically for the `MO(_DYN)` keycode as the "stop signal" so please don't use any fancy ways to access this layer, use the regular `MO()` modifier. To replay the macro, press either `DYN_MACRO_PLAY1` or `DYN_MACRO_PLAY2`. 865To start recording the macro, press either `DYN_REC_START1` or `DYN_REC_START2`. To finish the recording, press the `_DYN` layer button. The handler awaits specifically for the `MO(_DYN)` keycode as the "stop signal" so please don't use any fancy ways to access this layer, use the regular `MO()` modifier. To replay the macro, press either `DYN_MACRO_PLAY1` or `DYN_MACRO_PLAY2`.
866 866
867If the LED-s start blinking during the recording with each keypress, it means there is no more space for the macro in the macro buffer. To fit the macro in, either make the other macro shorter (they share the same buffer) or increase the buffer size by setting the `DYNAMIC_MACRO_SIZE` preprocessor macro (default value: 256; please read the comments for it in the header). 867If the LED-s start blinking during the recording with each keypress, it means there is no more space for the macro in the macro buffer. To fit the macro in, either make the other macro shorter (they share the same buffer) or increase the buffer size by setting the `DYNAMIC_MACRO_SIZE` preprocessor macro (default value: 128; please read the comments for it in the header).
868 868
869For the details about the internals of the dynamic macros, please read the comments in the `dynamic_macro.h` header. 869For the details about the internals of the dynamic macros, please read the comments in the `dynamic_macro.h` header.
870 870