Dee Newcum

Some points: **I predict there will be demand for QMK/ZMK-style macros** (e.g. keyboard layers, double-tap keys, etc), and maybe even for hooking up an HDMI capture card and responding to...

The implementation is basically complete. [This is the code](https://github.com/DeeNewcum/pi400kb/blob/record_macros/pi400.c#L210-L250). \*shrug\* If you'd rather not integrate it into the main project, I can maintain it as a parallel fork.

> And then input-event-codes.h provides all the K_ key codes input-event-codes.h's values are different from the USB HID values. For instance, input-event-codes.h defines escape as 0x01, but in USB HID...

> so storing constants for them is a recipe for angry Belgians. Ahh, I see. Thanks for the info.

I'm a little confused what #define NO_OUTPUT is for, or whether the call to prechecks() should be wrapped in it.

USB OTG can only run on the USB-C port. There are designs out there that allow you to plug a data cable in separately from a power cable, e.g. https://elmorlabs.com/product/usb-c-power-data-switch-for-raspberry-pi-4/

[This fork](https://github.com/DeeNewcum/pi400kb/blob/record_macros/pi400.c#L196-L208) might be easier to modify, the shortcut keys aren't hard-coded. You can see the full list of available keycodes [here](https://github.com/DeeNewcum/pi400kb/blob/record_macros/gadget-hid.h#L37).