>Hi Viv!
>
>It seems that the issue here has to do more with wait states, than any other specific situations affecting the timer. I modified your previous example as below. Some may call this cheating, however my point is that it would be impossible to predict the occurence, or otherwise manage, wait states in VFP.
The help on autoyield=.F. says:
The instance of Visual FoxPro does not process pending Windows events between each line of user program code.
All pending Windows events are placed in a queue, and the events in the queue are processed when DOEVENTS is issued or a wait state occurs. A wait state occurs when Visual FoxPro is waiting for input from the user. The WAIT command does not create a wait state.Your code suggests that we have discovered a BUG (versions 7 and 9 tested).
WAIT WINDOW [sometext] NOWAIT indeed does not create a wait state. However, your code
WAIT WINDOW TIMEOUT [somevalue] appears to create a wait state!
It is about time that somebody from MS jumps in here!
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
