On Wed May 21 09:30:48 2025 +0000, Huw Davies wrote:
Should we be doing this for both `DRV_FREE` and `DRV_CLOSE`?
Sorry for the delay.
Before only the `DRV_FREE` case contained the call to `MIDI_CALL( midi_release, NULL );`, whis is causes the thread leave its loop. But in this failure case through `CloseDriver` just the `DRV_CLOSE` case is reached, so I put both together. If we just wait in the `DRV_CLOSE` case the thread never leaves its loop.
I can make the close case distinct with a second line midi_release and the wait, and not touching `DRV_FREE` if this is desired?