Re: Semi-multithreaded application in VB6
- From: Matthias Julius <jnews@xxxxxxxxxxxxxx>
- Date: Fri, 16 Dec 2005 13:18:43 -0500
"Steve Gerrard" <mynamehere@xxxxxxxxxxx> writes:
> Question for you: where are you doing your DoEvents? The user won't be able to
> intervene except where you yield enough to let a button click get through. That
> would seem to be the place for your flag check as well.
There are a number of wait times in the cycle. You are raising a good
point here. If there is only a chance of a click event to get through
during those wait times it doesn't make sense to check this flag.
But, there is also a sub called by a timer periodically that might set
it. I presume your point is true for timer events as well.
And there are calls to dll functions that take some time to complete.
I don't know whether they block processing of events or not.
Matthias
.
- Follow-Ups:
- Re: Semi-multithreaded application in VB6
- From: Steve Gerrard
- Re: Semi-multithreaded application in VB6
- References:
- Semi-multithreaded application in VB6
- From: Matthias Julius
- Re: Semi-multithreaded application in VB6
- From: J French
- Re: Semi-multithreaded application in VB6
- From: Matthias Julius
- Re: Semi-multithreaded application in VB6
- From: J French
- Re: Semi-multithreaded application in VB6
- From: Matthias Julius
- Re: Semi-multithreaded application in VB6
- From: Steve Gerrard
- Semi-multithreaded application in VB6
- Prev by Date: Free help authoring tool...
- Next by Date: Install MSDN on different drive?
- Previous by thread: Re: Semi-multithreaded application in VB6
- Next by thread: Re: Semi-multithreaded application in VB6
- Index(es):
Relevant Pages
|