7.8 KiB
Macro shortcuts: Send a whole string when pressing just one key
Instead of using the ACTION_MACRO function, you can simply use M(n) to access macro n - n will get passed into the action_get_macro as the id, and you can use a switch statement to trigger it. This gets called on the keydown and keyup, so you'll need to use an if statement testing record->event.pressed (see keymap_default.c).
const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt) // this is the function signature -- just copy/paste it into your keymap file as it is.
{
switch(id) {
case 0: // this would trigger when you hit a key mapped as M(0)
if (record->event.pressed) {
return MACRO( I(255), T(H), T(E), T(L), T(L), W(255), T(O), END ); // this sends the string 'hello' when the macro executes
}
break;
}
return MACRO_NONE;
};
A macro can include the following commands:
- I() change interval of stroke in milliseconds.
- D() press key.
- U() release key.
- T() type key(press and release).
- W() wait (milliseconds).
- END end mark.
So above you can see the stroke interval changed to 255ms between each keystroke, then a bunch of keys being typed, waits a while, then the macro ends.
Note: Using macros to have your keyboard send passwords for you is possible, but a bad idea.
Advanced macro functions
To get more control over the keys/actions your keyboard takes, the following functions are available to you in the action_get_macro function block:
record->event.pressed
This is a boolean value that can be tested to see if the switch is being pressed or released. An example of this is
if (record->event.pressed) {
// on keydown
} else {
// on keyup
}
register_code(<kc>);
This sends the <kc> keydown event to the computer. Some examples would be KC_ESC, KC_C, KC_4, and even modifiers such as KC_LSFT and KC_LGUI.
unregister_code(<kc>);
Parallel to register_code function, this sends the <kc> keyup event to the computer. If you don't use this, the key will be held down until it's sent.
layer_on(<n>);
This will turn on the layer <n> - the higher layer number will always take priority. Make sure you have KC_TRNS for the key you're pressing on the layer you're switching to, or you'll get stick there unless you have another plan.
layer_off(<n>);
This will turn off the layer <n>.
clear_keyboard();
This will clear all mods and keys currently pressed.
clear_mods();
This will clear all mods currently pressed.
clear_keyboard_but_mods();
This will clear all keys besides the mods currently pressed.
update_tri_layer(layer_1, layer_2, layer_3);
If the user attempts to activate layer 1 AND layer 2 at the same time (for example, by hitting their respective layer keys), layer 3 will be activated. Layers 1 and 2 will also be activated, for the purposes of fallbacks (so a given key will fall back from 3 to 2, to 1 -- and only then to 0).
Naming your macros
If you have a bunch of macros you want to refer to from your keymap, while keeping the keymap easily readable, you can just name them like so:
#define AUD_OFF M(6)
#define AUD_ON M(7)
#define MUS_OFF M(8)
#define MUS_ON M(9)
#define VC_IN M(10)
#define VC_DE M(11)
#define PLOVER M(12)
#define EXT_PLV M(13)
As was done on the Planck default keymap
Timer functionality
It's possible to start timers and read values for time-specific events - here's an example:
static uint16_t key_timer;
key_timer = timer_read();
if (timer_elapsed(key_timer) < 100) {
// do something if less than 100ms have passed
} else {
// do something if 100ms or more have passed
}
It's best to declare the static uint16_t key_timer; outside of the macro block (top of file, etc).
Example: Single-key copy/paste (hold to copy, tap to paste)
With QMK, it's easy to make one key do two things, as long as one of those things is being a modifier. :) So if you want a key to act as Ctrl when held and send the letter R when tapped, that's easy: CTL_T(KC_R). But what do you do when you want that key to send Ctrl-V (paste) when tapped, and Ctrl-C (copy) when held?
Here's what you do:
static uint16_t key_timer;
const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt)
{
switch(id) {
case 0: {
if (record->event.pressed) {
key_timer = timer_read(); // if the key is being pressed, we start the timer.
}
else { // this means the key was just released, so we can figure out how long it was pressed for (tap or "held down").
if (timer_elapsed(key_timer) > 150) { // 150 being 150ms, the threshhold we pick for counting something as a tap.
return MACRO( D(LCTL), T(C), U(LCTL), END );
}
else {
return MACRO( D(LCTL), T(V), U(LCTL), END );
}
}
break;
}
}
return MACRO_NONE;
};
And then, to assign this macro to a key on your keyboard layout, you just use M(0) on the key you want to press for copy/paste.
Dynamic macros: record and replay macros in runtime
In 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).
To enable them, first add a new element to the planck_keycodes enum -- DYNAMIC_MACRO_RANGE:
enum planck_keycodes {
QWERTY = SAFE_RANGE,
COLEMAK,
DVORAK,
PLOVER,
LOWER,
RAISE,
BACKLIT,
EXT_PLV,
DYNAMIC_MACRO_RANGE,
};
Afterwards create a new layer called _DYN:
#define _DYN 6 /* almost any other free number should be ok */
Below these two modifications include the dynamic_macro.h header:
#include "dynamic_macro.h"`
Then define the _DYN layer with the following keys: DYN_REC_START1, DYN_MACRO_PLAY1,DYN_REC_START2 and DYN_MACRO_PLAY2. It may also contain other keys, it doesn't matter apart from the fact that you won't be able to record these keys in the dynamic macros.
[_DYN]= {
{_______, DYN_REC_START1, DYN_MACRO_PLAY1, _______, _______, _______, _______, _______, _______, _______, _______, _______},
{_______, DYN_REC_START2, DYN_MACRO_PLAY2, _______, _______, _______, _______, _______, _______, _______, _______, _______},
{_______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______},
{_______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______}
},
Add the following code to the very beginning of your process_record_user() function:
if (!process_record_dynamic_macro(keycode, record)) {
return false;
}
To 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.
If 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).
For the details about the internals of the dynamic macros, please read the comments in the dynamic_macro.h header.