mirror of
https://github.com/qmk/qmk_firmware.git
synced 2025-02-27 01:56:43 +00:00
16 lines
8.2 KiB
JavaScript
16 lines
8.2 KiB
JavaScript
|
import { _ as _export_sfc, c as createElementBlock, o as openBlock, a8 as createStaticVNode } from "./chunks/framework.DyMmIvSC.js";
|
|||
|
|
const __pageData = JSON.parse('{"title":"Dynamic Macros: Record and Replay Macros in Runtime","description":"","frontmatter":{},"headers":[],"relativePath":"feature_dynamic_macros.md","filePath":"feature_dynamic_macros.md"}');
|
|||
|
|
const _sfc_main = { name: "feature_dynamic_macros.md" };
|
|||
|
|
const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="dynamic-macros-record-and-replay-macros-in-runtime" tabindex="-1">Dynamic Macros: Record and Replay Macros in Runtime <a class="header-anchor" href="#dynamic-macros-record-and-replay-macros-in-runtime" aria-label="Permalink to "Dynamic Macros: Record and Replay Macros in Runtime""></a></h1><p>QMK supports temporary macros created on the fly. We call these Dynamic Macros. They are defined by the user from the keyboard and are lost when the keyboard is unplugged or otherwise rebooted.</p><p>You can store one or two macros and they may have a combined total of 128 keypresses. You can increase this size at the cost of RAM.</p><p>To enable them, first include <code>DYNAMIC_MACRO_ENABLE = yes</code> in your <code>rules.mk</code>. Then, add the following keys to your keymap:</p><table><thead><tr><th>Key</th><th>Alias</th><th>Description</th></tr></thead><tbody><tr><td><code>QK_DYNAMIC_MACRO_RECORD_START_1</code></td><td><code>DM_REC1</code></td><td>Start recording Macro 1</td></tr><tr><td><code>QK_DYNAMIC_MACRO_RECORD_START_2</code></td><td><code>DM_REC2</code></td><td>Start recording Macro 2</td></tr><tr><td><code>QK_DYNAMIC_MACRO_PLAY_1</code></td><td><code>DM_PLY1</code></td><td>Replay Macro 1</td></tr><tr><td><code>QK_DYNAMIC_MACRO_PLAY_2</code></td><td><code>DM_PLY2</code></td><td>Replay Macro 2</td></tr><tr><td><code>QK_DYNAMIC_MACRO_RECORD_STOP</code></td><td><code>DM_RSTP</code></td><td>Finish the macro that is currently being recorded.</td></tr></tbody></table><p>That should be everything necessary.</p><p>To start recording the macro, press either <code>DM_REC1</code> or <code>DM_REC2</code>.</p><p>To finish the recording, press the <code>DM_RSTP</code> layer button. You can also press <code>DM_REC1</code> or <code>DM_REC2</code> again to stop the recording.</p><p>To replay the macro, press either <code>DM_PLY1</code> or <code>DM_PLY2</code>.</p><p>It is possible to replay a macro as part of a macro. It's ok to replay macro 2 while recording macro 1 and vice versa but never create recursive macros i.e. macro 1 that replays macro 1. If you do so and the keyboard will get unresponsive, unplug the keyboard and plug it again. You can disable this completely by defining <code>DYNAMIC_MACRO_NO_NESTING</code> in your <code>config.h</code> file.</p><div class="tip custom-block"><p class="custom-block-title">TIP</p><p>For the details about the internals of the dynamic macros, please read the comments in the <code>process_dynamic_macro.h</code> and <code>process_dynamic_macro.c</code> files.</p></div><h2 id="customization" tabindex="-1">Customization <a class="header-anchor" href="#customization" aria-label="Permalink to "Customization""></a></h2><p>There are a number of options added that should allow some additional degree of customization</p><table><thead><tr><th>Define</th><th>Default</th><th>Description</th></tr></thead><tbody><tr><td><code>DYNAMIC_MACRO_SIZE</code></td><td>128</td><td>Sets the amount of memory that Dynamic Macros can use. This is a limited resource, dependent on the controller.</td></tr><tr><td><code>DYNAMIC_MACRO_USER_CALL</code></td><td><em>Not defined</em></td><td>Defining this falls back to using the user <code>keymap.c</code> file to trigger the macro behavior.</td></tr><tr><td><code>DYNAMIC_MACRO_NO_NESTING</code></td><td><em>Not Defined</em></td><td>Defining this disables the ability to call a macro from another macro (nested macros).</td></tr><tr><td><code>DYNAMIC_MACRO_DELAY</code></td><td><em>Not Defined</em></td><td>Sets the waiting time (ms unit) when sending each key.</td></tr></tbody></table><p>If the LEDs 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 adding the <code>DYNAMIC_MACRO_SIZE</code> define in your <code>config.h</code> (default value: 128; please read the comments for it in the header).</p><h3 id="dy
|
|||
|
|
const _hoisted_24 = [
|
|||
|
|
_hoisted_1
|
|||
|
|
];
|
|||
|
|
function _sfc_render(_ctx, _cache, $props, $setup, $data, $options) {
|
|||
|
|
return openBlock(), createElementBlock("div", null, _hoisted_24);
|
|||
|
|
}
|
|||
|
|
const feature_dynamic_macros = /* @__PURE__ */ _export_sfc(_sfc_main, [["render", _sfc_render]]);
|
|||
|
|
export {
|
|||
|
|
__pageData,
|
|||
|
|
feature_dynamic_macros as default
|
|||
|
|
};
|