S
Sam (Deleted User)
Guest
Hello community.
I've noticed using non-async functions like WaitForSingleObject() and system() in a *.DLL can make the Windows Runner crash, if it is waiting on a process to close, and the user tries to click on or interact with the main game window.
I reported this as a bug on the YYG helpdesk, but I was wondering, in the meantime, if there was any alternitve functions that don't crash the Windows Runner?
I've tried using the system() function, in an *.SO library, un-forked, on Linux, and while the application is waiting, you can try to click on or mess with the window and it doesn't crash, so this is clearly a Windows-only related issue.
Thanks for any help or advice!
Samuel
I've noticed using non-async functions like WaitForSingleObject() and system() in a *.DLL can make the Windows Runner crash, if it is waiting on a process to close, and the user tries to click on or interact with the main game window.
I reported this as a bug on the YYG helpdesk, but I was wondering, in the meantime, if there was any alternitve functions that don't crash the Windows Runner?
I've tried using the system() function, in an *.SO library, un-forked, on Linux, and while the application is waiting, you can try to click on or mess with the window and it doesn't crash, so this is clearly a Windows-only related issue.
Thanks for any help or advice!
Samuel