Patrick Reisert
Patrick Reisert
The reason is that midir is trying to abstract from the platform, but the platforms vary significantly in their MIDI APIs. On Windows, for example, the underlying API for MIDI...
Thanks for the PR! I have a few questions: - What exactly does this allow you to do that you can't do without it? - Is the same pattern applied...
I thought about removing it, but there is a difference compared to closure captures, which make it still useful: Rust's lifetime system does not know about a closure type that...
Yeah, probably there is no usecase that couldn't also be solved with a channel (sender/receiver). But I'd like to have some more feedback from others ... Concerning the `Option`, I...
Note to self: Actually there is already a branch (which I forgot about) where the `user_data` is removed: https://github.com/Boddlnagg/midir/tree/remove-userdata
@vklquevs Would it be useful if `MidiInput::connect` also lets you get the userdata back? I can have a look if I can change that. In general I think that I...
@vklquevs: Can you have a look at #44 and evaluate whether that would be useful to you so that you wouldn't need the user data anymore? I'm still trying to...
It is usually the case that the client name will be contained in the port name, and I agree that this redundancy is bad, but I don't think this will...
https://github.com/atsushieno/cmidi2
https://crates.io/crates/midi-control also mentions that it might want to support MIDI 2.0 eventually