Skip to main content

Reacting to events

onChartRendered: (chart) => {}

Fired after the seating chart is fully rendered. The rendered chart is passed in as a parameter.

onChartRenderingFailed: (chart) => {}

Fired when there's an error when rendering the chart. The event manager object is passed in as a parameter, to allow you to destroy it if needed.

onChartRerenderingStarted: (chart) => {}

Fired before a chart rerendering starts. The rendered chart is passed in as a parameter.

onObjectSelected: (selectedObject) => {}

Fired when an object (seat, table, etc) gets selected.

onObjectDeselected: (deselectedObject) => {}

Fired when an object (seat, table, etc) gets de-selected.

onObjectClicked: (clickedObject) => {}

Fired when the user clicks or taps on an object (seat, table, etc). Note that this event will be fired even if the object is not selectable.

onFullScreenOpened: () => {}

Fired when the user clicks the fullscreen button.

onFullScreenClosed: () => {}

Fired when the user closes the fullscreen view.

onSubmitSucceeded: () => {}

Fired when the event manager state is successfully saved on the seats.io servers: e.g. when the user clicks the 'Apply changes' button (any mode), when the user adds a new channel (in manageChannels mode).

onSubmitFailed: () => {}

Fired when the event manager failed to save its state on the seats.io servers: e.g. when the user clicks the 'Apply changes' button (any mode) but the operation failed.

Object Properties

Some of these callbacks take a bookable object (i.e. a seat, a table, a booth) as a parameter.

To see the different properties available on these objects, please refer to Renderer Object Properties.