Protected _isActive state of Cursor
Readonly scaleScale of the series
Attach object to an legendBox entry
Series itself for fluent interface
Object which has to be attached
Flag that indicates whether the Attachable should be hidden or not, when its respective Entry is clicked.
By default, entries are assigned a smooth looking gradient based on the component color. If this flag is true, then this is skipped, and exact component solid fill is used instead.
Clear all previous data pushed to the series.
Object itself for fluent interface.
Permanently destroy the component.
To fully allow Garbage-Collection to free the resources used by the component, make sure to remove any references to the component and its children in application code.
let chart = ...ChartXY()
let axisX = chart.getDefaultAxisX()
// Dispose Chart, and remove all references so that they can be garbage-collected.
chart.dispose()
chart = undefined
axisX = undefined
Object itself for fluent interface
Get whether series is taken into account with automatic scrolling and fitting of attached axes.
By default, this is true for all series.
true default, axes will take series into account in scrolling and fitting operations.
false, axes will ignore series boundaries.
Beta
Get override behavior for when this series is formatted to be displayed by a cursor.
Override callback or undefined
Introduced in v6.0.0, the state and definition of this API is not finalized. It may change in future versions without regard to backwards compatibility if there is significant cause from user feedback.
Get theme effect enabled on component or disabled.
A theme can specify an Effect to add extra visual oomph to chart applications, like Glow effects around data or other components.
Whether this effect is drawn above a particular component can be configured using the setEffect method.
// Example, disable theme effect from a particular component.
Component.setEffect(false)
For the most part, theme effects are enabled by default on most components.
Theme effect is configured with effect property.
Boolean that describes whether drawing the theme effect is enabled around the component or not.
Get heatmap intensity interpolation mode.
Heatmap intensity interpolation mode selection.
Invalidate range of heatmap intensity values starting from first sector and annulus, updating coloring if a Color look up table (LUT) has been attached to the series (see setFillStyle).
// Example, 3x3 grid full invalidation.
const heatmapSeries = PolarChart.addHeatmapSeries({
sectors: 3,
annuli: 3
})
heatmapSeries.invalidateIntensityValues([
// Annulus 0 intensity values.
[0, 0, 0],
// Annulus 1 intensity values.
[1, 1, 1],
// Annulus 2 intensity values.
[0, 2, 0],
])
Data interpretation basis is defined by dataOrder property from when the series was created.
invalidateIntensityValues can trigger warnings when used controversially.
In production applications, these can be controlled with warnings.
Object itself for fluent interface.
Matrix containing intensity values for each data slot of the grid.
Invalidate a partial range of heatmap intensity values, updating coloring if a Color look up table (LUT) has been attached to the series (see setFillStyle).
// Example, 100x10 grid invalidate partial section of grid.
const heatmapSeries = PolarChart.addHeatmapSeries({
sectors: 100,
annuli: 10
})
heatmapSeries.invalidateIntensityValues({
// Index of first invalidated annulus.
iAnnulus: 5,
// Index of first invalidated sector.
iSector: 10,
// Intensity values matrix. It's dimensions imply the amount of invalidated sectors and annuli.
values: [
// 1st invalidated annuli intensity values.
[1, 1, 1, 1, 1],
// 2nd invalidated annuli intensity values.
[2, 2, 2, 2, 2],
// 3rd invalidated annuli intensity values.
[1, 0, 0, 0, 1],
// 4th invalidated annuli intensity values.
[0, 1, 0, 1, 0],
// 5th invalidated annuli intensity values.
[0, 0, 1, 0, 0],
],
})
invalidateIntensityValues can trigger warnings when used controversially.
In production applications, these can be controlled with warnings.
Object itself for fluent interface.
Partial invalidation information, where values is an intensity value matrix, iSector the first affected sector and iAnnulus the first affected annulus.
Subscribe onDispose event.
This event is triggered whenever the ChartComponent is disposed.
// Example usage
lineSeries.onDispose(() => {
console.log('lineSeries was disposed')
})
lineSeries.dispose()
Token of subscription
Event handler function
Subscribe to highlight object event. This is called whenever an object is highlighted.
Token that can be used to unsubscribe from the event.
Function that is called when event is triggered.
Add event listener to Mouse Click Event
Token of the event listener
Event listener for Mouse Click Event
Add event listener to Mouse Double Click Event
Token of the event listener
Event listener for Mouse Double Click Event
Add event listener to Mouse Down Event
Token of the event listener
Event listener for Mouse Down Event
Subscribe to Mouse Drag event
Subscribe to Mouse Drag Start event
Subscribe to Mouse Drag Stop event
Add event listener to Enter Event
Token of the event listener
Event listener for Mouse Enter Event
Add event listener to Mouse Leave Event
Token of the event listener
Event listener for Mouse Leave Event
Add event listener to Mouse Move Event
Token of the event listener
Event listener for Mouse Move Event
Add event listener to Mouse Up Event
Token of the event listener
Event listener for Mouse Up Event
Subscribe to Mouse Wheel event
Token of subscription
Event handler function
Subscribe to Touch End event
Token of subscription
Event handler function
Subscribe to Touch Move event
Token of subscription
Event handler function
Subscribe to Touch Start event
Token of subscription
Event handler function
Register new event listener to visibleStateChanged event.
Event listener for visibleStateChanged
Set component highlight animations enabled or not. For most components this is enabled by default.
// Example usage, disable highlight animations.
component.setAnimationHighlight(false)
Object itself
Animation enabled?
Set whether series is taken into account with automatic scrolling and fitting of attached axes.
By default, this is true for all series.
By setting this to false, any series can be removed from axis scrolling/fitting.
// Example syntax, remove series from automatic scrolling / fitting.
LineSeries.setAutoScrollingEnabled(false)
Object itself for fluent interface.
true default, axes will take series into account in scrolling and fitting operations.
false, axes will ignore series boundaries.
Configure whether cursors should pick on this particular series or not.
// Example, prevent chart auto cursor from snapping to a series.
LineSeries.setCursorEnabled(false)
Related API:
Beta
Set override behavior for when this series is formatted to be displayed by a cursor. This can be used to alter and expand on cursor formatting done for a specific series, either by the library's default cursor formatters or even the users own cursor formatters defined on chart level.
// Example syntax, add extra row to display a custom data property
series.setCursorFormattingOverride((hit, before) => {
if (!isHitSampleXY(hit)) return before
const customPropertyValue = data[hit.iSample].customProperty
return [...before, ['ASD', '', customPropertyValue.toFixed(3)]]
})
To use this with users own cursor formatters, you can use useCursorFormatterSeriesOverride:
// Example syntax, define custom cursor formatting with support for series overrides
chart.setCursorFormatting((_, __, hits) => {
return [
[hits[0].axisX.formatValue(hits[0].x)],
...hits.map((hit) => useCursorFormatterSeriesOverride(hit, [['Y:', '', hit.axisY.formatValue(hit.y)]])).flat(),
]
})
Object itself.
Introduced in v6.0.0, the state and definition of this API is not finalized. It may change in future versions without regard to backwards compatibility if there is significant cause from user feedback.
Override callback or undefined
Set theme effect enabled on component or disabled.
A theme can specify an Effect to add extra visual oomph to chart applications, like Glow effects around data or other components.
Whether this effect is drawn above a particular component can be configured using the setEffect method.
// Example, disable theme effect from a particular component.
Component.setEffect(false)
For the most part, theme effects are enabled by default on most components.
Theme effect is configured with effect property.
Object itself.
Theme effect enabled
Set fill style of heatmap series.
Supported fill styles:
Colors heatmap fill by looking color up from LUT based on heatmap intensity values.
// Example, color look up by intensity values.
heatmapSeries.setFillStyle(
new PalettedFill({
lut: new LUT({
steps: [
{ value: 0, color: ColorCSS('red') },
{ value: 20, color: ColorCSS('blue') },
],
interpolate: true,
}),
}),
)
Assign intensity values with invalidateIntensityValues.
Solid color for all heatmap cells. Supported for debugging purposes mainly.
Disables heatmap fill.
// Example, hide heatmap fill.
heatmapSeries
.setFillStyle(emptyFill)
Object itself for fluent interface.
FillStyle object or function which modifies current value.
Set state of component highlighting.
// Example usage
component.setHighlight(true)
component.setHighlight(0.5)
If highlight animations are enabled (which is true by default), the transition will be animated. As long as the component is highlighted, the active highlight intensity will be animated continuously between 0 and the configured value. Highlight animations can be disabled with setAnimationHighlight
Object itself
Boolean or number between 0 and 1, where 1 is fully highlighted.
Set highlight on mouse hover enabled or disabled.
Mouse interactions have to be enabled on the component for this to function as expected. See setMouseInteractions for more information.
Object itself for fluent interface.
True if highlighting on mouse hover, false if no highlight on mouse hover
Beta
Set icon of the chart component. This is displayed in legends and by default cursor formatters.
const image = new Image()
image.src = 'image.png'
const icon = chart.engine.addCustomIcon(image)
ChartComponent.setIcon(icon)
Object itself.
Released as beta feature in v5.2.0 feature may still change according to user feedback and experiences.
Icon
Set heatmap intensity interpolation mode.
'disabled' or undefined: Interpolation disabled; draw data exactly as it is.
'bilinear': Each PIXEL is colored based on an Bi-linearly interpolated intensity value based on the 4 closest real intensity values.
Object itself for fluent interface.
Heatmap intensity interpolation mode selection.
Set component mouse interactions enabled or disabled.
Disabling mouse interactions means that the objects below this component can be interacted through it.
Possible side-effects from disabling mouse interactions:
Object itself for fluent interface
Specifies state of mouse interactions
Sets the name of the Component updating attached LegendBox entries
Object itself
Name of the Component
Set element visibility.
Object itself.
true when element should be visible and false when element should be hidden.
Method for solving the nearest data point to a given coordinate on screen.
// Example syntax
chart.onSeriesBackgroundMouseClick((_, event) => {
const nearest = series.solveNearest(event, 'show-nearest')
console.log(nearest)
})
SolveResult object or undefined.
Reference coordinate on web page as client coordinates. This can for example be directly an Event object.
Optional control for solve nearest behavior
Match legend entry style to reflect components own style.
By default, entries are assigned a smooth looking gradient based on the component color. If this flag is true, then this is skipped, and exact component solid fill is used instead.
Series for visualizing a Polar Heatmap with a static sector and annuli count. Has API for fast modification of cell values.
PolarHeatmapSeriesis optimized for high resolution data. For example, 1 degree precision or less along Radial Axis, and up to more than 2000 samples along Amplitude Axis. There is no hard cap on how much data you can put into a polar heatmap, the limit is the running device's GPU memory. Generally several million data points are no problem.Created with addHeatmapSeries.
Frequently used API: