Killing function execution in a third-party DLL writen in C++ from within a VB6 program
I 've the following situation. From within a Visual Basic 6 app I call a function in a third-party DLL. This function waits for a physical event in order to terminate (eg.: touch a scanner screen), but that does not always happen.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.