Here’s what I do currently.

[list=1:2tishzqf][:2tishzqf]FSOUND_Stream_OpenFile with the file name[/:m:2tishzqf]
*:2tishzqf FSOUND_Stream_Close[/:m:2tishzqf]
*:2tishzqf Execute steps 1-4[/

This causes access violations.

I think I have solved the problem by posting a Windows message from the callback; the message handler executes what was previously in the callback routine. This suggests that there are some issues with ‘pulling the rug out from underneath whatever calls the callback function’ that perhaps should be addressed.

Either that, or it should be better documented what you can and can’t do in the SetEndCallback callback function.

  • You must to post comments
Showing 0 results
Your Answer

Please first to submit.