Create a printable shortcut legend for your macropad
KM16 Macropad puts sixteen keys and three knobs on the desk, but a printed legend should describe your actual configuration rather than a generic product diagram. The goal is to recover the meaning of an unfamiliar control at a glance. Make the reference from your saved assignments, including the application each shortcut targets and any layer you must activate first.
What information belongs beside a key label?
Record a short action name, the emitted input and its destination. For example, a label could say Find in editor, followed by the combination you configured. Keep the exact binding separate from the friendly name so a later software change does not make the label misleading. A name alone cannot help you diagnose an incorrect event.
Use the physical arrangement in front of you as the reference. Do not infer a grid shape from a product name or another owner's photograph. If a knob has different assignments for each rotation direction, show both. Only include a press action when your particular control and configuration support one.
How should layers be represented?
Give every active layer a name tied to a task, such as Review or Research. State how you enter and leave it. A momentary layer and a persistent toggle create different expectations, so the legend should make that behaviour explicit rather than presenting two unlabeled diagrams.
If there is no clear way to identify the current layer, simplify the layout before printing it. A reference sheet can explain a mode, but it cannot tell you which mode the hardware is currently using. Fewer well-understood mappings may be preferable to a dense sheet of rarely used alternatives.
What makes the printout easy to maintain?
Add the configuration filename or profile name and a revision date. Keep an editable copy next to the exported settings. When a shortcut changes, update the source document before printing another version. This prevents a stale paper reference from becoming the authority over the actual device configuration.
Put dependencies in a small note: destination application, host remapper and any required startup process. Microsoft's Keyboard Manager guidance is one example of why a background utility belongs in the setup record. A hardware key can appear broken when that dependency is simply absent.
How do you check the legend before relying on it?
Ask yourself to follow the sheet without relying on memory. Test every listed action in a harmless workspace and compare the result with its label. Correct ambiguous names and remove unused controls from the active legend. The KM16 Macropad product page describes the device, while the printed reference should describe the working setup you actually maintain.