Riskable

I just merged upstream (everything's up to date again). Any chance you can take a look?

OK I think I've resolved the "clean public interface" issue which was the last remaining hurdle (I think). @TeXitoi What do you think?

Frankly I'm surprised it doesn't already have this feature! Add me to the list of folks that want this primarily so I can have the keyboard send unicode characters (e.g....

If you give me some tips I'll do my best and hopefully submit a PR! I never intended to, but I've become quite familiar with the way Keyberon works developing...

Well let me state that I wrote a tool (https://github.com/liftoff/HumanInput) for JavaScript that takes strings as input and converts them to keystrokes (that it listens for--as opposed to executing them)...

Almost forgot: If possible, we also need a way to serialize the macro format as well so we can store it in a config somewhere (e.g. EEPROM). Not sure if...

How about something that accumulates? Like: ```rust event_delay = 10; // ms between keydown/keypress/keyrelease ke = KeyEvent::new(event_delay); ke.add_keydown(LCtrl); ke.add_keydown(LShift); ke.add_keydown(U); ke.add_keypress(Kb1); ke.add_keypress(F); ke.add_keypress(Kb4); ke.add_keypress(A); ke.add_keypress(F); ke.add_keyrelease(LCtrl); // Or maybe just...

Just realized a better way would be to just chain the calls: ```rust ke = KeyEvent::new() .keydown(LCtrl) .keydown(LShift) .keydown(U) .keypress(Kb2) .keypress(Kb6) .keypress(Kb3) .keypress(A) .keyrelease(); ```

That'll work! For a mod name how about, "KeyMacro" since that's basically what it is?

I started trying to implement this myself but I've run into an issue: The way the keydown `State` seems to get handled via `keycode(&self)` but a key *release* gets handled...