Hi Bill,

Sounds like a catch-22 to me. You want to use a timer to check if a page has finished loading but the timer events which check this don't fire until the page has finished loading...

I suppose you could set a 'Waiting for page' flag when you start loading and clear this in the handling procedure. The timer events would still be queued but could be ignored/discarded once the flag was cleared.

Or, since a backlog of timer events fire 'at once', you could use the SECONDS() function to discard events less than 250ms (do you really need to check that often?) after the previous one.

Out of curiosity - why do you say the Browser events aren't reliable enough ?

Regards,
Viv



>>
________________
I have a timer with an interval 250. Sometimes when I'm trying to open a stubborn page in the web browser control my timer events stack up. Then when the page finishes loading, all the timer events execute one after another.

Is there someway to get the timer to quit stacking up the events and just trigger it once when the page finishes loading?

The timer is primarily just checking to see if the page has finished loading (DownLoadComplete() and DocumentComplete() are not reliable enough).