-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MinidInput::connect take self ownership #90
Comments
I agree that this is probably not the most flexible design, but I think the original reason was that some backend required it, or was otherwise very hard to write without this "limitation". Looking at the code now (a few years after I implemented it), I think it was the ALSA backend, where If anyone is familiar with ALSA and can chime in and offer a better solution, I'd be happy to change this. |
Yes I have finally found a workaround with message passing. Thank you for the explanation. I am on MacOSX but I have several linux too. I will try to take a look. |
This seems to be related to #86 |
Because of Boddlnagg/midir#90, this is some of the weirdest Rust code I've ever written.
Hi,
I don't understand why this function takes self ownership. This prevents to reuse MidiInput instance. Moreover I have noticed that MidiInput::new raises an InitError when the same name is reused for the connection. Is there a way to reuse a MidiInput instance ?
The text was updated successfully, but these errors were encountered: