>With Autoyield = .F. the Timer code never executes (either in the main loop or in the subseqent wait state) regardless of the inclusion of DOEVENTS - the interrupt is effectively discarded.
>
>With Autoyield = .T. and DOEVENTS included the timer code executes in the main loop as expected. But with no DOEVENTS the timer event is queued and only executes in the wait state - the .Counter will initially be 0, hitting OK at intervals will show the previously queued events being consumed.
>
>So the grey area is 'Can the timer code EVER execute with AUTOYIELD = .T. unless there's a wait state' ? My hunch would be 'No' but I wouldn't bet the ranch on it. OTOH, I'd be interested to see someone positively demonstrate the opposite :-}
>It would also be interesting to see how many interrupts would be queued!
>
>Regards,
>Viv

hi Viv,

See Storin's answer message#1103809 which makes sense if you read through the docs

I can only say that I've seen it happen. On rare occasions, I agree, but it happened

The only thing we're missing is the definition of a wait state.

Think we need clarification from someone from Microsoft on this one

Can it or can't it ?