-
Notifications
You must be signed in to change notification settings - Fork 677
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
Question: WinUI interfering with MIDI APIs #6663
Comments
I added an artificial message loop after my call to while (GetMessage(out var msg, default, 0, 0))
{
TranslateMessage(in msg);
DispatchMessage(in msg);
} |
It appears to be a bug with the .NET debugger. I filed an issue below but I'll leave the WinUI team close this question in case they have insights. |
@MikeHillberg thoughts? |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I am using the
midiIn
APIs to get a callback when I press notes on my connected (piano) keyboard. This works fine with a console application, but I never get any callbacks in my WinUI application. The midi objects are created in theApplication.OnLaunched
method, so they should have main thread affinity.Does WinUI does not run a standard Win32
PeekMessage
/DispatchMessage
loop on the main thread? Is there a way to make it do so?It would be possible to create a separate thread for my midi objects and run my own message loop there, but this is a good amount of extra complexity that I would rather avoid, and I'm not sure that would fix the issue.
Thanks for any suggestions
The text was updated successfully, but these errors were encountered: