You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see some weirdness while trying to interface with the WaveOut API in Windows (8.1, 64-bit, go1.4.2).
A callback I defined in Go and passed to WaveOut is supposed to be triggered multiple times by the lowlevel library on certain events. After a certain point these callbacks don't seem to run in Go but running my app through apimonitor shows that the lowlevel library actually tries to fire them:
I tried to reproduce the issue with some standalone code, this is what I have (Note: Of course the actual issue might not be related, I don't know exactly what the winmm API and the sound interface driver are doing. Plus my low-level coding skills are lame so the whole thing could be completely wrong):
Looks like I have to get a gcc toolchain up and running on windows for import "C" to work. I guess it would be easier to cross-compile the whole thing :)
I see some weirdness while trying to interface with the WaveOut API in Windows (8.1, 64-bit, go1.4.2).
A callback I defined in Go and passed to WaveOut is supposed to be triggered multiple times by the lowlevel library on certain events. After a certain point these callbacks don't seem to run in Go but running my app through apimonitor shows that the lowlevel library actually tries to fire them:
I tried to reproduce the issue with some standalone code, this is what I have (Note: Of course the actual issue might not be related, I don't know exactly what the winmm API and the sound interface driver are doing. Plus my low-level coding skills are lame so the whole thing could be completely wrong):
Sample dll:
Sample Go:
What I expect to see on the terminal is
but I only see:
The text was updated successfully, but these errors were encountered: