Fired when a chart in the set was manually resized
Fired when the chart was cleared
Fired when a context menu for one or more objects should be displayed
Fired when a new chart will be created
Fired when a new chart was created
Fired when an object was double clicked
Fired when a legend entry or a custom button (e.g. "select") of a legend entry was clicked
For special legend entries that do not directly reference an object, the object
parameter will be set to the Chart instead.
Fired when a legend entry was hovered
falsy if loading finished successfully; otherwise contains an error
Fired when all requested time series and generators finished loading, or loading was canceled
NOTE: this event is never fired while the "isLoading" property of the controller is true. This is especially relevant if the application is using the toggleLoading method, the event might be delayed. E.g. if the controller finishes loading data, but the application called toggleLoading(true), the event will not be fired until the application calls toggleLoading(false).
Fired when a message can be shown to the user to inform him about an event
an i18n independant identifier unique to the respective event
the actual message
if the message references an object in the chart, it will be provided here
Fired when an object was added to the underlying chartset
Fired during placement, when an object was created but not yet added to a chart
NOTE: object was not yet added to the Controllers hierarchy at this time. Some options might
Fired when an object that previously triggered objectCreated
was discarded
Fired when an objects flags changed
Fired when the highlighted object changes If no object is highlighted, parameter will be null
Fired if the hovered object changes; If no object is hovered, parameter will be null
Fired when an object (e.g. a tool) was modified
Fired when an object was moved to a new parent, scale and/or position NOTE: for Charts, both oldParent and newParent will always be null
Fired when an object that previously triggered objectCreated
was placed in the chart
This event is triggered up to two times; the third parameter indicates if the tool was just placed in a chart but there are still other handles to be placed (false), or if placement was completely finished (true).
So basically for tools that just have one handle it will only trigger once; twice for all others.
NOTE: event can be null if placement is non interactive e.g. calling addTool with a point for a tool that has only one handle will finish immediately without requiring any user interaction
Fired when an object was removed from the underlying chartset
Fired when an object was renamed
Fired when an object was replaced by or changed to another object; currently only triggered when replacing timeseries.
Fired when an object was selected or deselected; If an object was deselected, parameter will be null
Fired when a timeseries received new data
Fired when a selection menu should be displayed. The ui should call the provided callback with the object selected by the user.
fired when a loader replaces the given timeseries identifier with a different one, e.g. to honor user preferences.
uis may need to update to show the new identifier
true if user interaction (e.g. touch or click) is in progress
Fired when something in the chart changed, or the interaction state changed. The flags indicate the kind of change(s) that occured: data, viewport, state etc.
Note: By reacting to just viewport and state changes, it is possible to figure out when exactly the output of serialize will change. The much more frequent data changes do not need to be considered in this case.
Note: Using the interaction state it is possible to "suppress" changes while an interaction is active; e.g. it might make sense to wait until an interaction is finished before running code that reacts to viewport changes, because while the interaction is in progress, it might rapidly change again.