I ran a simple test to confirm that VB6 form events are not threaded. I had event "A" initiate event "B". Event "B" would wait a period of time (looping on DoEvents) before displaying a message. If events "A" and "B" were threaded, event "B" would continue after initiating "A" and change the message before "A" had a chance to display it. Well needless to say the message was not changed until the second occurance of event "A"; meaning that control remained with event "B" until it displayed its message, and then control returned to event "A". On return to event "A" the message was changed for display on the second occurance of event "A".
It known that VB.Net has threading constructs: the question; is there a way to accomplish threading in VB6, possible using some Windows API function?
X.
It known that VB.Net has threading constructs: the question; is there a way to accomplish threading in VB6, possible using some Windows API function?
X.