Resolution of the timer event, in milliseconds.
定时器的分辨力，毫秒。
The interval for the timer event is calculated in real world time.
时间事件的间隔期是由现实世界的时间来计算的。
Nor do browsers pass any information about the timer event to these functions.
浏览器并不将关于计时器事件的任何信息传递给这些函数。
First, we must detect that we have received the final timer event in the burst.
首先，我们必须检测是否已经收到了连续计时器事件中的最后一个计时器事件。
When this message is sent into the flow, a single timer event occurs immediately.
当将此消息发送到流中时，将立即发生唯一的计时器事件。
Once this single timer event occurs, the timeout request is considered completed.
一旦发生这个唯一的计时器事件，则将该超时请求视为已完成。
Your timer event functions don't do much more than your cursor event functions.
计时器事件函数没有鼠标事件函数那么复杂。
Norr do browsers pass any information about the timer event to these functions.
浏览器并不将关于计时器事件的任何信息传递给这些函数。 。
To work around this developers should stop the timer when processing a timer event.
要想解决这个矛盾，开发者可以在处理一个timer事件的时候停止时间计数器的计数。
This state object is passed to your timer callback function during each timer event invocation.
在每一个定时器事件被调用时该state对象作为一个参数传递给你的定时回调函数。
This information let us determine if we are processing the last timer event for a given request.
可利用此信息确定是否在处理给定请求的最后一个计时器事件。
The third parameter (dueTime) allows you to specify when the initial timer event should be fired.
第三个参数(dueTime)让你定义一个引发初始定时器事件的时间。
This has the effect of making the timer event fire 2 seconds after developer code stops executing.
这样做的结果是使得timer事件在代码停止执行后的两秒钟才被触发。
Property that specifies the number of milliseconds that pass between one timer event and the next.
属性，该属性指定一个计时器事件与下一个计时器事件之间间隔的毫秒数。
Specifying either 0 or Timeout.Infinite for this parameter will disable subsequent timer event invocations.
给该参数定义一个0或者Timeout . Infinite可以阻止后续的定时器事件调用。
These two fields represent the original number of timer events requested and the current timer event number.
这两个字段表示所请求的计时器事件原始数量和当前计时器事件数量。
Of course, a message that immediately produces one timer event isn't very useful. A more practical message might be.
当然，立即产生一个计时器事件的消息并不是很有用。
The timer is not periodic; you set it when the timer event is triggered, and then the event is removed from the event queue.
计时器不是周期性的；当触发计时器事件时设置它，然后从事件队列中删除事件。
If we do detect that this is the final timer event in the burst, then we must build a new control message to setup for the next burst.
如果确实检测到这是连续事件中的最后一个计时器事件，则必须构建一个新的控制消息，以设置下一组连续事件。
Hence, the value of the tickCounter variable was incremented five times before the processing of the first timer event was completed.
因此，在第一个定 时器事件处理完成之前tickCounter变量被增加了5次。
You implemented code to: hook cursor events for all three browser event models, start and cancel both types of timers, and hook their timer events.
实现了以下功能的代码：针对所有三种浏览器事件模型连接鼠标事件，启动和取消两种类型的计时器，并连接它们的计时器事件。
The node begins timings as soon as the containing message flow has been deployed, and the first timer event occurs as soon as the flow is deployed.
一旦包含的消息流被部署，该节点将立即开始计时，第一个计时器事件将立即发生。
This is because during the five seconds that the first timer event was sleeping, the timer kept on generating Elapsed events on different worker threads.
这是因为在这5秒期间第一个定时器事件正在睡眠，而定时器却在不同的工作者线程上继续产生时间消失事件。
You want the tooltip to appear near the cursor when the timeout event occurs in Pause state, but browsers do not pass the cursor position to timer events.
当在Pause状态下出现timeout事件时，希望工具提示出现在鼠标光标附近，但是浏览器没有将鼠标位置传递给计时器事件。
But suppose the broker was down for 15 minutes and we set up a timer for once every minute, will the broker create 15 timer event messages when it restarts?
但假定代理停止工作15分钟，而设置了一个每分钟进行一次计时的计时器，代理是否会在重新启动时创建15条计时器消息？
Remember that StartTime represents the time of the first timer event, not the last, so adding the value of "BurstInterval" correctly sets the time for the next event.
请记住，StartTime表示第一个计时器事件的时间，而不是最后一个事件的时间，因此正确添加“BurstInterval”的值可设置下一个事件的时间。
They create a trivial timer event object that contains only an event type -- either timeout or timetick -- and pass it to the same handleEvent method that handles cursor events.
它们仅仅创建一个简单的计时器事件对象，其中只包含一种事件类型 ——timeout或者timetick，并将它传递给处理鼠标事件的同一个 handleEvent方法。
To maximize code reuse, the sample application calls the same ShowTimerEventFired method from all three different types of timer events. Here are the three timer event handlers.
为了最大限度的代码重用，三种不同类型的定时器事件都调用了同样的ShowTimerEventFired方法，下面就是三个定时器事件的处理函数。
All these timer event messages are sent on to the "BuildTimeoutMessage" compute node for further processing. All we need to do in this node is to move the timeout message to the XML domain.
所有这些计时器事件消息都将发送到“BuildTimeout Message”计算节点进行进一步处理。
All these timer event messages are sent on to the "BuildTimeoutMessage" compute node for further processing. All we need to do in this node is to move the timeout message to the XML domain.
所有这些计时器事件消息都将发送到“BuildTimeout Message”计算节点进行进一步处理。
应用推荐