Is there any reason a webtimer should not get to its action event?
The timer is on a containercontrol, and it is used to have the container refresh reliably. When the timer’s action event occurs, it calls a method to show an error message. Sometimes the action event never happens. I can tell when things are/are not happening because I have a bunch of logging statements in the code.
(Note: Of course, it always works when I run it either locally or on our test site.)
So, if I need to update some information on the page (say receiving an error message from a service), I thought using a timer was the right thing to do because the page would update at the end of the event (the timer’s action event). If that’s no reliable, is there something else I can do? (BTW, I set the timer’s mode to multiple on the chance it might not fire reliably but that it might fire sooner or later. I turn it off in the action event.)
As I understand it, the only way to get something to change on a page is to have some event end. The action event of a timer is suggested.
We’re getting a reply back from a service. Sometimes things are okay, and processing continues. Sometimes there is an error (e.g. user has entered bad data), and we want to show our users an error message so they may correct things.
So, when I receive and error message, I start the timer. In the timer’s action event I present the error message. This works reliably on my computer and on our tester’s computer. It does not work on the director’s iMac, but it does work on is MacBook Air and iPad.
I have numerous logging statements. If the action event fires, it should write to the log. So, I know where things are happening (or not).
If there is another way to get the error message to appear, I will try it.
Drag a generic object to the WebContainer/WebPage
Make it’s super “Timer”
Add the Action event with the Msgbox inside
In the Open event of the WC/WP, set the period :
TimerRefresh.Period = 100
No need to have any shorter period, an average round trip is already over 150 ms.