Christof Laenzlinger

my current attempt looks like this: ```rust impl Button { pub fn handle(&mut self, action: Action) -> Option where B: Buffer + BufferMut + BufferDefault + BufferResize, { // depending...

Thanks a lot for this hint with `BufferTryResize` This really helped. I am now trying an interface like the following: ```rust impl Button { pub fn handle(&mut self, action: Action)...

What is not clear to me: How do I find out how large the resulting buffer should be that has to be sent over the wire? For example a TimingClock...

Ok, this makes the above approach valid again. I was scared that this this information (length) would have to be retreived from somewhere else which would have been a bit...

Yes I can confirm that upgrading to 0.6.4 fixes the length issue with realtime messages. Could you maybe provide some feedback to the API that was proposed above. Does this...

Thanks for you reply and also for `try_new_with_buffer`. I have changed the code now to use a non-generic API as you suggested. Since the state of the button is stored...

One nest problem, where I am now struggling, is the initial question that I had: There are some actions, which trigger multiple messages to be returned. For example. I want...

@BenLeadbetter Thank you so much for your continiued support and help for exploring these ideas! If I understand your idea correctly, then you split the buffer into multiple junks with...

There are the MMC messages, which are SysEx based. When using a DAW this is a very useful feature for a Midi controller. DAWs (although they can of course be...

Thanks @BenLeadbetter for all your suggestions. I am currently working with the following API: Each controller type's `handle()` function returns a ControllerMessages struct which has a similar interface than the...