>>>You might set a breakpoint for the Timer() event.
>>
>>How is that done??
>
>Open the debugger:
>
>
set step on
>
>Open the breakpoint window:
>
>Press Ctrl-B
>
>Under "Location", type "Timer" and press ENTER.
>
>Keep the debugger window open. The next time a Timer event fires, the debugger should interfere, perhaps allowing you to figure out which timer was executed.
At Breakpoint it now says: at "timer"
But nothing happens...
>You might also put a breakpoint for "when expression changes": _tally, or "when expression is true": _tally = 1.
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.
