Jon Black

Hi all. I'm really sorry that I haven't responded to any of the merge requests. I'm open to giving someone contributor permissions to work through some of them. Sadly, I'm...

Let's see if I understand. It sounds like you have more than two states `A -> B -> C`. When you transition from `A -> B` the handler for state...

Thanks, now I understand your state machine, but sadly not your problem. What is working as you'd like it to?

Thanks, that's a better explanation. This is (maybe) a bug. The problem is that the state in the machine is [set after the callbacks are called](https://github.com/jonblack/arduino-fsm/blob/master/Fsm.cpp#L99). If we want to...

I've drawn out the state machine you've described so I can visualise it better: 

> During a transition, the machine has no state...or a IN_FLIGHT/NULL state. > The exit() state is in the state it is exiting and the enter() state, the one >...

> It's a 6$ clone of https://lametric.com/ with a wemos D1 mini and 2 or 3 max7219 LED Matrix. That's an interesting project. I'd love to read a blog post...

Motherboard is back. This coming weekend is quite busy. If I don't manage it, I'll do it the weekend after. Sorry it can't be sooner.

@Thelmos Are you proposing that `STATE_MESSAGE_onstate()` be called for each state every time `runMachine` is called or just for the current state?

@redge76 Why do you want to avoid calling things in `loop()`? I like the idea of an `on_state` callback. It avoids having to deal with recursion from calling trigger twice;...