>>
_Tally and timers Thread #
1102133 Message #
1102133>>
>
>What an interesting reading, especially close to the end of that thread.
>
>Anyway, timers in VFP are based on Windows timers and are triggered when VFP processes Windows events. When AutoYield =.T., approximately every 200 milliseconds VFP processes Windows message before executing the next command. Therefore, it is possible for Timer events to fire between any two consecutive commands, SELECT-SQL and the next command are not special.
This *was* my understanding about timers: A timer does not fire during a SELECT-SQL and a next line that tests for the _TALLY. It only fires on moments that an input (most notably from a user) is possible.
As a consequence of that understanding, there is *no* need to save/restore _TALLY in the timer event's code.
After having read your comment, this is about to become my understanding about timers: If _Visual FoxPro.autoyield=.T. a timer can also fire after a SELECT-SQL and before the next line that tests for the _TALLY.
As a consequence of that understanding, there *is* a need to save/restore _TALLY in the timer event's code if autoyield=.T..
If this is the case, I can live with it. But I also beg you to
document this in the next beta at two places: Autoyield property and Timer object.
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.
