要真正响应事件,必须在实现文件内定义事件表。
To actually respond to events, you must define the event table within your implementation files.
图5举例说明了适配器和应用程序事件表之间的交互。
Figure 5 illustrates the interaction between an adapter and an application event table.
你需要一个未来事件表,还要一个过去事件表。
You need a chart of future events, and you need a chart of past events.
如您所预期的一样,END_EVENT _table宏指出事件表的末尾。
The END_EVENT_TABLE macro, as you might expect, signifies the end of the event table.
您可以用类似的方式装载用于其他事件类型的表。
You can load the tables for the other event types in a similar way.
表1.初始测试环境:1个普通代理、1个Mbean、每分钟是10个事件。
Table 1. Initial test environment: 1 GA, 1 MBean, 10 events per minute.
该字段决定了在日程表的什么地方显示事件。
This field determines where to display the event on the calendar.
如果是正数,则将日程表事件显示到起始日期的右边(或将来)。
Positive Numbers will display calendar events to the right (or future) of the start date.
剩下的惟一一步是用于显示约会事件的日程表视图。
The only step remaining is the calendar view to display appointment events.
如果是负数,则将日程表事件显示到起始日期的左边(或之前)。
Negative Numbers will display calendar events to the left (or prior) to the start date.
第一种方法是管理连续日程表事件的一种简单而有效的方法。
This first approach is a simple and efficient method to manage sequential calendar events.
但是时间表在本周末此次悲剧事件前就停滞了。
But that timeline was drawn up before the tragic incident this weekend over Wardak.
也可以用它展现事件的时间表。
Column3只是显示日程表事件的文本值。
Column3 simply displays the text value for the calendar event.
构建一个简单的事件日程表。
以下是他们之间冲突的关键事件的时间表。
Below is a timeline of key events in the conflict between them.
要求你的病人制定好肿瘤相关事件的一览表。
Ask the patient for a schedule of his cancer-related events.
要求你的病人制定好肿瘤相关事件的一览表。
Ask the patient for a schedule of his cancer-related events.
应用推荐