Users interacting with content generate events that consist of three pieces of information <content,view,event>. The content attribute is the name of the content that the event occurred on. The view attribute is the name of the view the event occurred on. The event attribute is the name of the event. An example event might be: <Employees,LeftTable,doubleClick>. In this section we will describe the events that each kind of content can generate.
click:{key}[:{value}], doubleClick:{key}[:{value}], refresh, select
click, doubleClick, refresh, select
click[:{url}], doubleClick[:{url}], refresh
click[:{url}], doubleClick[:{url}], refresh
refresh, select
click:{key}[:{value}], doubleClick:{key}[:{value}], refresh, select
click:{key}[:{value}], doubleClick:{key}[:{value}], refresh, select
click:{key}[:{value}], doubleClick:{key}[:{value}], refresh
Elements written in braces like this: {xxx} are substituted by dynamic values depending on where the event occurs. These are usually preceded by a colon symbol (:). Elements written in square brackets like this [yyy] are optional, and may not be present if the information is not available. For example, a bar chart will have both a key and value string available, whereas a pie chart will only offer a key.
Here's a description of when each event is sent:
A click event is sent whenever a user clicks on a supporting view. The click may include extra information after the event name, for example click:{url} if the click occurs over a mouse-sensitive region in a glint or report, or click:{key}[:{value}] if the click occurs over a chart.
A doubleClick event is sent whenever a user clicks twice on the same view within a short period of time and without moving the mouse. A click event will always precede a doubleClick event.
A refresh event is sent each time a view is rendered because the underlying data has changed. It is not necessary to respond to this event to update dependent views, this is handled internally.
A select action occurs when a user changes the selection state of those contents that maintain a selection (e.g. table). It is not necessary to respond to this event to update dependent views (e.g. those that depend on view:XXX.selected), this is handled internally.