Behavior of multiple midi callbacks about tulipcc HOT 2 CLOSED

Good catch. I want the midi_callback to receive the MIDI bytes that triggered the callback, but you can only send a single small integer from C (where we get the MIDI bytes) to Python in Tulip right now. This is due to the way MP calls are scheduled: https://github.com/orgs/micropython/discussions/14164 . In that discussion, you can see that some people work around this for e.g bluetooth packets by having a ring buffer. I haven't tried that yet, but it probably makes sense for Tulip?

The only-allowing a single callback is sad for me because then the midi.py callback (that boots when Tulip does) would be the only one, and we couldn't have a separate one for the sliders in juno6 when it boots.

A new solution I just invented in my head is we do only have a single C -> Python callback, and let the always running midi.py receive it, but the midi.py callback then delegates out to other Python-registered callbacks. Like we make a midi_add_callback in pure Python in midi.py instead of worrying about mp_sched_schedule. I think that works too.

from tulipcc.

Check out this proposed fix, works for me:

#227

from tulipcc.