Re: Timer event just...doesn't happen
- From: erewhon@xxxxxxxxxx (J French)
- Date: Wed, 31 May 2006 08:46:39 GMT
On Tue, 30 May 2006 15:35:57 +0200, "Robert" <noone@xxxxxxxxxxx>
wrote:
No DoEvents in my code (except if VB forces me at swordpoint, so to speak),
and certainly none in this project. Still, in an executable...I'd better
take a look at this. Thanks for the idea.
A timer will never fire again until it has completed its 'event'
If you are going off to something complex, maybe a 3rd party DLL or
OCX, then maybe those are doing a DoEvents, which would explain why
your other timers are firing, and that one is not.
.
- References:
- Timer event just...doesn't happen
- From: Robert
- Re: Timer event just...doesn't happen
- From: J French
- Re: Timer event just...doesn't happen
- From: Robert
- Timer event just...doesn't happen
- Prev by Date: How to generate system Error in WinXP ?
- Next by Date: Re: Strange problem in function treturning values
- Previous by thread: Re: Timer event just...doesn't happen
- Next by thread: Re: Timer event just...doesn't happen
- Index(es):
Relevant Pages
|