summaryrefslogtreecommitdiff
path: root/digital/io-hub
AgeCommit message (Expand)Author
2011-04-07digital/io-hub: fix supply connector polarityNicolas Schodet
2011-04-07digital/io-hub: larger spoke-servoNicolas Schodet
2011-04-06digital/io-hub: add a hole to screw spoke boardsNicolas Schodet
2011-03-25digital/io-hub: add spoke-servoNicolas Schodet
2011-03-25digital/io-hub: add silkscreenNicolas Schodet
2011-03-25digital/io-hub: routeNicolas Schodet
2011-03-22digital/io-hub: add basic and indus spokes, refs #79Nicolas Schodet
2011-03-22digital/io-hub: place components, refs #79Nicolas Schodet
2011-03-22digital/io-hub: add PCB, route outer supply, refs #79Nicolas Schodet
2011-03-22digital/io-hub: filter Vadc, remove servo supply, refs #79Nicolas Schodet
2011-01-13digital/io-hub: new io-hub, schematic, refs #79Nicolas Schodet
108'>108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158
# Macros - Send multiple keystrokes when pressing just one key

QMK has a number of ways to define and use macros. These can do anything you want- type common phrases for you, copypasta, repetitive game movements, or even help you code. 

**Security Note**: While it is possible to use macros to send passwords, credit card numbers, and other sensitive information it is a supremely bad idea to do so. Anyone who gets ahold of your keyboard will be able to access that information by opening a text editor.

# Macro Definitions

By default QMK assumes you don't have any macros. To define your macros you create an `action_get_macro()` function. For example:

```c
const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt) {
	if (record->event.pressed) {
		switch(id) {
			case 0:
				return MACRO(D(LSFT), T(H), U(LSFT),