Protected _isFlag that is set whenever Panel or any scale is resized.
Will be handled before plot to update scale and trigger resize event just once per frame.
Readonly backgroundInterface for attaching listeners to user interaction events (click, pointerenter, etc.) on chart background.
// Example syntax
chart.background.addEventListener('click', (event) => {
console.log(event)
})
For syntax examples, refer to EventInterface. Available event keys are listed under LCJSInteractionEventMap
Please note that many chart types have a separate "series background" (area enclosed by axes), which has its own separate events. This is accessed via seriesBackground property.
Readonly coords3D Coordinate system selector to use with translateCoordinate function, which lets users translate coordinates between different 3D coordinate systems.
Readonly coordsSelector for "client" Coordinate System.
This references the coordinate system used in HTML.
It starts at top left of the web page and is measured in pixels.
For example, { x: 100, y: 20 } corresponds to 100 pixels from left and 20 pixels from top.
JavaScript events are tracked and HTML elements are positioned in the client coordinate system.
This selector can be used for translating client coordinates to other coordinate systems and vice versa. For example, in order to:
See translateCoordinate for more detailed use case information and example usage.
Readonly coordsSelector for "relative" Coordinate System.
This coordinate system is relative to the bottom left corner of the Control (chart/dashboard/etc.), and is measured as pixels.
For example, { x: 100, y: 20 } corresponds to 100 pixels from left and 20 pixels from bottom.
This selector can be used for two purposes:
Positioning LCJS UI elements in pixels:
// Position UI element in pixels by supplying `Control.coordsRelative` as its positioning system.
const textBox = Control.addUIElement(UIElementBuilders.TextBox, Control.coordsRelative)
.setOrigin(UIOrigins.LeftBottom)
.setPosition({ x: 100, y: 20 })
Translations between coordinate systems:
Use with translateCoordinate method to translate coordinates from "relative" to another coordinate system.
Readonly coords3D Coordinate system selector to use with translateCoordinate function, which lets users translate coordinates between different 3D coordinate systems.
Readonly engineInterface for end user API of the LCJS engine. It provides some useful capabilities over the area enclosed by a single LCJS context (which can be just a single chart, or a Dashboard with several charts).
Readonly seriesInterface for attaching listeners to user interaction events (click, pointerenter, etc.) on chart series background (area enclosed by axes).
// Example syntax
chart.seriesBackground.addEventListener('click', (event) => {
console.log(event)
})
For more syntax examples, refer to EventInterface. Available event keys are listed under LCJSInteractionEventMap
Readonly titleInterface for attaching listeners to user interaction events (click, pointerenter, etc.) on chart title.
// Example syntax
chart.title.addEventListener('click', (event) => {
console.log(event)
})
For syntax examples, refer to EventInterface. Available event keys are listed under LCJSInteractionEventMap
Scale for panel area in percentages (0-100).
While it is not functionally equal to this, using coordsRelative coordinate system is preferred (more confidence for long term support).
Convenience getter property that does the same as getDefaultAxisX.
Convenience getter property that does the same as getDefaultAxisX.
Convenience getter property that does the same as getDefaultAxisX.
Convenience getter property that does the same as getDefaultAxisX.
Convenience getter property that does the same as getDefaultAxisX.
Convenience getter property that does the same as getDefaultAxisX.
Create Series for visualization of large sets of individually configurable 3D Boxes.
Example usage:
// Construct a grid of vertical boxes.
const data = [
{ x: 0, z: 0 },
{ x: 1, z: 0 },
{ x: 0, z: 1 },
{ x: 1, z: 1 }
]
// Map coords into **BoxData**.
.map( coords => {
const height = Math.random() * 100
return {
xCenter: coords.x,
yCenter: height / 2,
zCenter: coords.z,
xSize: 1,
ySize: height,
zSize: 1
}
})
const chart = lightningChart().Chart3D()
const boxSeries = chart.addBoxSeries()
.invalidateData( data )
BoxSeries3D.
Optional options: SeriesOptionsAdd manually controlled Cursor object. These have exactly same functions as built-in cursors but they can be freely controlled by application logic.
const cursor = chart.addCursor()
Styling works same as built-in cursors (e.g. setCursor).
Position is set using setPosition method and displayed content using setResultTable(table => table.setContent(...))
For more details, see Developer documentation > Features > Cursor > Manual cursors
Cursor object.
Builder for cursor. Can be used to tweak a handful of properties which can't be changed during runtime.
Add callback function to be triggered when specified event is fired.
// Example syntax
object.addEventListener('click', (event) => {
console.log(event)
})
Some classes also report extra information about the interacted object with the second parameter:
// Most series share information about interacted data point
series.addEventListener('click', (event, info) => {
console.log(info)
})
Optional third parameter allows registering event handlers that will automatically remove themselves after first trigger:
// Example this listener will only fire once
object.addEventListener('click', (event) => {})
Each class has its own list of supported events.
Some events are from HTML standard (click, pointerdown, etc.),
while others are own events from LightningChart JS (dispose, resize, etc.)
To find what events are available, you can try following:
TypeScript enabled, just write addEventListener and see what possible event types the IDE suggests. These APIs are strongly typed, and even the callback event will be correctly typed.K type parameter extends.Callback function that is triggered when event is fired.
Optional options: LCJSAddEventListenerOptionsOptional extra configuration options.
Add a legendbox.
Legendbox is a type of UI element, that floats inside the chart/component it is created inside. It can be freely moved around with user interactions, as well as positioned in application code.
The purpose of legendbox is to describe the series and other visual components of the chart, by displaying their names and colors. Hovering over a series' legendbox entry will highlight that series, and clicking on the entry will toggle that series' visibility.
Legendbox alignment:
Alignment of legendbox can be selected by supplying one of the available LegendBoxBuilders to addLegendBox:
// Default (vertical) LegendBox.
const legendBox = ChartXY.addLegendBox()
// Horizontal LegendBox.
const horizontalLegendBox = ChartXY.addLegendBox(LegendBoxBuilders.HorizontalLegendBox)
Custom Legendbox positioning:
By default LegendBoxes are placed on the right side, or bottom of the chart (depending on alignment).
A custom location can be configured with UIElement API:
Position coordinate system is specified when creating legendbox.
addLegendBox( LegendBoxBuilders.VerticalLegendBox )
// Position = [0, 100] as percentages.
.setPosition({ x: 50, y: 50 })
addLegendBox( LegendBoxBuilders.VerticalLegendBox, chart.coordsRelative )
// Position = pixels.
.setPosition({ x: 300, y: 100 })
addLegendBox( LegendBoxBuilders.VerticalLegendBox, { x: chartXY.getDefaultAxisX(), y: chartXY.getDefaultAxisY() } )
// Position = Axis values.
.setPosition({ x: 5, y: 5 })
LegendBox
LegendBoxBuilder. If omitted, VerticalLegendBox will be selected. Use LegendBoxBuilders for selection.
Optional parameter for altering the coordinate system used for positioning the LegendBox. Defaults to whole Chart in percentages [0, 100].
Method for adding a new LineSeries3D to the chart.
This Series type for visualizing a collection of { x, y, z } coordinates by a continuous line stroke.
LineSeries3D is optimized for massive amounts of data - here are some reference specs to give an idea:
To learn more about its features and usage, refer to LineSeries3D.
New series.
Optional options: SeriesOptionsOptional options: MeshModel3DOptionsReadonly options for the created series.
Method for adding a new PointLineSeries3D to the chart.
This Series type for visualizing a collection of { x, y, z } coordinates by a continuous line stroke and markers.
PointLineSeries3D is optimized for massive amounts of data - here are some reference specs to give an idea:
To learn more about its features and usage, refer to PointLineSeries3D.
New series.
Optional options: SeriesOptionsMethod for adding a new PointSeries3D to the chart.
This series type for visualizing a collection of { x, y, z } coordinates by different markers.
PointSeries3D is optimized for massive amounts of data - here are some reference specs to give an idea:
To learn more about its features and usage, refer to PointSeries3D.
Readonly configuration:
Some properties of PointSeries3D can only be configured when it is created. These arguments are all optional,
and are wrapped in a single object parameter:
// Example,
const pointCloudSeries3D = Chart3D.addPointSeries({
// Specify point series type as point cloud.
type: PointSeriesTypes3D.Pixelated
})
To learn about available properties, refer to PointSeriesOptions3D.
New series.
Optional options: PointSeriesOptions3D<T>Optional object with readonly configuration arguments for PointSeries3D.
Add a Series for visualizing a Surface Grid with a static column and grid count. Has API for fast modification of cell Y and Intensity values.
The grid is defined by imagining a plane along X and Z axis, split to < COLUMNS > (cells along X axis) and < ROWS > (cells along Z axis)
The total amount of < CELLS > in a surface grid is calculated as columns * rows. Each < CELL > can be associated with DATA from an user data set.
This series is optimized for massive amounts of data - here are some reference specs to give an idea:
To learn more about its features and usage, refer to SurfaceGridSeries3D.
Readonly configuration:
Some properties of SurfaceGridSeries3D can only be configured when it is created. Some of these arguments are optional, while some are required.
They are all wrapped in a single object parameter:
// Example,
const surfaceGridSeries = Chart3D.addSurfaceGridSeries({
columns: 100,
rows: 200,
})
To learn about these properties, refer to SurfaceGridSeries3DOptions.
For scrolling surface grid, see addSurfaceScrollingGridSeries.
Surface Grid Series.
Configuration parameters for Surface Grid Series.
Add a Series for visualizing a Surface Grid with API for pushing data in a scrolling manner (append new data on top of existing data).
The grid is defined by imagining a plane along X and Z axis, split to < COLUMNS > (cells along X axis) and < ROWS > (cells along Z axis)
The total amount of < CELLS > in a surface grid is calculated as columns * rows. Each < CELL > can be associated with DATA from an user data set.
This series is optimized for massive amounts of data - here are some reference specs to give an idea:
To learn more about its features and usage, refer to SurfaceScrollingGridSeries3D.
Readonly configuration:
Some properties of SurfaceScrollingGridSeries3D can only be configured when it is created. Some of these arguments are optional, while some are required.
They are all wrapped in a single object parameter:
// Example,
const surfaceScrollingGridSeries = Chart3D.addSurfaceScrollingGridSeries({
columns: 100,
rows: 200,
})
To learn about these properties, refer to SurfaceScrollingGridSeries3DOptions.
For static surface grid, see addSurfaceGridSeries.
Surface Scrolling Grid Series.
Configuration parameters for Surface Scrolling Grid Series.
Add a stand-alone UIElement using a builder.
Example usage:
addUIElement( UIElementBuilders.TextBox )
// Position = [0, 100] as percentages.
.setPosition({ x: 50, y: 50 })
addUIElement( UIElementBuilders.TextBox, chart.coordsRelative )
// Position = pixels.
.setPosition({ x: 300, y: 100 })
addUIElement( UIElementBuilders.TextBox, { x: chartXY.getDefaultAxisX(), y: chartXY.getDefaultAxisY() } )
// Position = Axis values.
.setPosition({ x: 5, y: 5 })
Object that fulfills interfaces: UIElementType (typeparam) and UIElement
Type of UIElement that is specified by 'builder'-parameter.
UIElementBuilder. If omitted, TextBoxBuilder will be selected. Use UIElementBuilders for selection.
Optional parameter for altering the coordinate system used for positioning the UIElement. Defaults to whole Chart in percentages [0, 100].
Beta
Clear zoom state history which is used by restorePreviousZoomState as well as any built-in "restorePrevious" user interactions.
// Example usage, set axis interval and ensure any previous zoom state history is deleted.
chart.axisX.setInterval({ start: 0, end: 100 })
chart.clearPreviousZoomStateHistory()
The order of above operations is important.
Object itself.
Introduced in v7.0.0. API may change according to user feedback.
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 active cursor formatter.
Cursor formatter.
Get current cursor behavior.
SolveNearestMode or undefined
Convenience method to get a tuple of the Charts X, Y and Z axes.
Equal to [Chart3D.getDefaultAxisX(), Chart3D.getDefaultAxisY(), Chart3D.getDefaultAxisZ()]
Intended for conveniently applying same modifications to all axes.
[Chart3D.getDefaultAxisX(), Chart3D.getDefaultAxisY(), Chart3D.getDefaultAxisZ()]
Get Array of all legend boxes created using addLegendBox method.
This will not include any legend boxes that were destroyed with dispose method.
Array of legend boxes.
Get series of a chart
Array of series
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 size of control as pixels.
For stand-alone component, the size will be equal to the size of its containing HTML <div> (Control.engine.container)
For component inside Dashboard, the size will only include the component itself, so size can be less than the size of containing HTML <div>.
Object with x and y properties { x: number, y: number }, where both are pixel values.
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 font of Chart title.
FontSettings object
Beta
Not to be confused with GlowEffect
Introduced in v7.0. API may be changed according to user feedback and reports.
Beta
Get currently active user interaction scheme. This does NOT return the last value supplied to setUserInteractions. Rather, it considers the current structure of the chart, all built-in defaults as well as overrides supplied by the user and returns the currently used interaction scheme.
Chart3DUserInteractions
Introduced in v7.0.0. API may change according to user feedback.
Remove event listener added using addEventListener.
The expected argument should be the exact same callback function that was supplied using addEventListener:
// Basic example syntax
const listener = () => {}
obj.addEventListener('click', listener)
obj.removeEventListener('click', listener)
// Basic boilerplate of custom interaction when user drags on an object
obj.addEventListener('pointerdown', (eventDown) => {
let prevCoord = eventDown
const handlePointerMove: LCJSInteractionEventListener<'pointermove'> = (eventMove) => {
const delta = { x: eventMove.clientX - prevCoord.clientX, y: eventMove.clientY - prevCoord.clientY }
prevCoord = eventMove
console.log(delta, eventMove.clientX, eventMove.clientY)
}
const handlePointerUp: LCJSInteractionEventListener<'pointerup'> = (eventUp) => {
window.removeEventListener('pointermove', handlePointerMove)
window.removeEventListener('pointerup', handlePointerUp)
}
window.addEventListener('pointermove', handlePointerMove)
window.addEventListener('pointerup', handlePointerUp)
})
Listener that was added using addEventListener.
Beta
Restore previous zoom state of all Axes.
Chart3D automatically follows the state of its axes. The previous state can be restored using this method.
// Example usage
chart.restorePreviousZoomState()
// Example, all properties
chart.restorePreviousZoomState({
animate: 1000, // 1000 ms animation
stopAxisAfter: true
})
Object itself.
Introduced in v7.0.0. API may change according to user feedback.
Optional opts: { Optional extra control options.
Capture rendered state in an image file. Prompts the browser to download the created file.
NOTE: The download might be blocked by browser/plugins as harmful. To prevent this, only call the method in events tied to user-interactions. From mouse-event handlers, for example.
Has two optional parameters which directly reference JavaScript API HTMLCanvasElement.toDataURL. For supported image formats, compression quality, Etc. refer to:
https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/toDataURL
Example usage:
// Download 'screenshot.png'
Panel.saveToFile('screenshot')
// Attempt download 'maybeNotSupported.bmp'
Panel.saveToFile('maybeNotSupported', 'image/bmp')
// Attempt download jpeg.file with specified compression quality
Panel.saveToFile('fileName', 'image/jpeg', 0.50)
If 'type' is not supported by browser, an Error will be thrown.
Name of prompted download file as string. File extension shouldn't be included as it is automatically detected from 'type'-argument.
Optional type: stringA DOMString indicating the image format. The default format type is image/png.
Optional encoderOptions: numberA Number between 0 and 1 indicating the image quality to use for image formats that use lossy compression such as image/jpeg and image/webp. If this argument is anything else, the default value for image quality is used. The default value is 0.92.
Set Chart3D zoom animation enabled.
When enabled, zooming with mouse wheel or trackpad will include a short animation.
This is enabled by default.
// Example syntax, disable zoom animation.
chart3D.setAnimationZoom(false)
Chart itself for fluent interface.
Boolean.
Disable/Enable all animations for the chart.
Affects:
Chart itself for fluent interface.
Boolean value to enable/disable all animations
Set FillStyle of chart background.
// Example usage,
ChartXY.setBackgroundFillStyle(new SolidFill({ color: ColorRGBA( 80, 0, 0 ) }))
Related API:
Transparent chart backgrounds:
LightningChart JS charts can be configured to be fully or partially transparent.
// Example, partially transparent chart
// Engine background exists under all LCJS components. In case of Dashboard, there is only 1 shared engine background.
chart.engine.setBackgroundFillStyle(emptyFill)
// Chart background covers every 1 chart. In case of Dashboard, every chart has its own chart background.
chart.setBackgroundFillStyle(new SolidFill({ color: ColorRGBA(0, 0, 0, 100) }))
// Some charts also have a separate series background.
chart.setSeriesBackgroundFillStyle(new SolidFill({ color: ColorRGBA(0, 0, 0, 100) }))
Object itself
FillStyle or function which mutates the active FillStyle.
Set LineStyle of chart background border stroke.
// Example usage,
ChartXY.setBackgroundStrokeStyle(new SolidLine({
thickness: 2,
fillStyle: new SolidFill({ color: ColorRGBA( 0, 255, 0 ) })
}))
Related API:
Object itself
LineStyle or function which mutates the active LineStyle.
Set the dimensions of the Scenes bounding box.
The bounding box is a visual reference that all the data of the Chart is depicted inside of. The Axes of the 3D chart are always positioned along the sides of the bounding box.
Example usage:
setBoundingBox( { x: 1.0, y: 1.0, z: 1.0 } )
setBoundingBox( { x: 1.0, y: 4.0, z: 1.0 } )
Object itself for fluent interface
Dimensions of bounding box. These values do not represent any "unit", only their relative ratios are considered.
Set style of 3D bounding box.
The bounding box is a visual reference that all the data of the Chart is depicted inside of. The Axes of the 3D chart are always positioned along the sides of the bounding box.
Example usage:
Chart3D.setBoundingBoxStrokeStyle(new SolidLine({
fillStyle: new SolidFill({ color: ColorHEX('#61ff61') }),
thickness: 5
}))
// Default value is SolidLine (note that a soft type cast is required for *TypeScript*).
Chart3D.setBoundingBoxStrokeStyle(( line: SolidLine ) => line
.setThickness( 10 )
)
Object itself for fluent interface.
Set automatic camera fitting enabled. This is enabled as the default configuration. Note that zooming in or out disables it automatically.
Object itself for fluent interface.
Boolean.
Set the location of camera in World Space, a coordinate system that is not tied to 3D Axes.
The camera always faces (0, 0, 0) coordinate.
The light source is always a set distance behind the camera.
Camera location in 3D space. Valid values are in the range [1, 5]. Note, that placing the camera too close to the bounding box is restricted.
Style chart cursor using a callback function. Available style APIs can depend on the type of chart.
// Example syntax
chart.setCursor((cursor) => cursor
.setGridStrokeXStyle(new SolidLine({
thickness: 1,
fillStyle: new SolidFill({ color: ColorRGBA( 255, 0, 0 ) })
}))
)
See Cursor2D, CursorXY or Cursor3D for all available methods for configuring the cursor.
Example usage:
// Example 1, disable Y Axis tick marker & grid line.
chart.setCursor((cursor) => cursor
.setTickMarkerYVisible(false)
.setGridStrokeYStyle(emptyLine)
)
// Example 2, style cursor ResultTable.
chart.setCursor((cursor) => cursor
.setResultTable((resultTable) => resultTable
.setOrigin(UIOrigins.LeftTop)
.setTextFillStyle(new SolidFill({ color: ColorRGBA(255, 0, 0) }))
.setTextFont((font) => font
.setSize(12)
.setFamily('sans-serif')
)
.setBackground((background) => background
.setFillStyle(new SolidFill({ color: ColorRGBA(0, 0, 0, 0) }))
)
)
)
// Example 3, style cursor TickMarker X.
chart.setCursor((cursor) => cursor
.setTickMarkerX((tickMarker: UIPointableTextBox) => tickMarker
.setTextFont((font) => font.setWeight('bold'))
.setTextFillStyle(new SolidFill({ color: ColorRGBA(0, 255, 0) }))
.setBackground((background) => background.setFillStyle(emptyFill).setStrokeStyle(emptyLine)),
)
)
Object itself for fluent interface.
Set cursor formatting, controlling the text displayed in built-in cursor.
chart.setCursorFormatting((_, hit, hits) => {
return [
['Cursor pointing at'],
[hit.series], // returning a series will display the series color and its name automatically.
['X', '', hit.axisX.formatValue(hit.x)], // utilizing axis formatValue is useful for considering active zoom level and type of axis
['Y', '', hit.y.toFixed(2)], // empty string '' results in gap between cells
[{ text: 'Example', font: { weight: 'bold' }, fillStyle: fillRed }] // any cell can also be styled individually
]
})
Before overriding default cursor formatting, it is recommended to check if using setUnits or configuring Axis cursor formatting would be enough.
In order to use series specific data properties (e.g. Heatmap sample "intensity"),
you should use type guards to assert the type of the SolveResult:
// Example of using type guard in cursor formatter
Chart.setCursorFormatting((chart, hit, hits) => {
if (!isHitHeatmap(hit)) return undefined
return [hit.intensity.toFixed(1)]
})
More details in Developer documentation (Features > Cursor).
Object itself
Callback function for cursor formatting.
Set cursor behavior. This affects both built-in cursor as well as any custom cursor connected using setCustomCursor.
For possible values see SolveNearestMode.
Additionally, you can supply undefined value to disable cursor completely.
// Example, show 1 nearest solve result only
chart.setCursorMode('show-nearest')
// Example, disable cursor
chart.setCursorMode(undefined)
// Example, enable interpolation
chart.setCursorMode('show-all-interpolated')
Object itself
SolveNearestMode or undefined
Connect a custom cursor to the chart. This has 2 effects:
Custom cursors are still affected by other cursor behavior controls such as:
setCursorEnabledThe custom cursor can be anything defined by the user, such as:
// Example of plugging in a custom cursor
chart.setCustomCursor((event) => {
if (event) {
// Display custom cursor
} else {
// Hide custom cursor
}
})
Object itself
undefined to restore built-in cursor or callback function that should be triggered to display custom cursor.
Set padding around Chart in pixels.
// Example 1, specify complete padding (four sides).
ChartXY.setPadding({ left: 16, right: 16, top: 32, bottom: 8 })
// Example 2, specify only single padding.
ChartXY.setPadding({ right: 64 })
Object itself
Number with pixel margins for all sides or datastructure with individual pixel paddings for each side. Any side can be omitted, only passed values will be overridden.
Beta
Select 3D projection type.
Defaults to 'perspective'
Object itself.
Introduced in v6.0. Previously 'perspective' was always applied. 'orthographic' behavior may be modified in future.
Projection type.
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 FillStyle of series background (area behind series).
// Example usage,
ChartXY.setSeriesBackgroundFillStyle(new SolidFill({ color: ColorRGBA( 60, 0, 0 ) }))
Related API:
Transparent chart backgrounds:
LightningChart JS charts can be configured to be fully or partially transparent.
// Example, partially transparent chart
// Engine background exists under all LCJS components. In case of Dashboard, there is only 1 shared engine background.
chart.engine.setBackgroundFillStyle(emptyFill)
// Chart background covers every 1 chart. In case of Dashboard, every chart has its own chart background.
chart.setBackgroundFillStyle(new SolidFill({ color: ColorRGBA(0, 0, 0, 100) }))
// Some charts also have a separate series background.
chart.setSeriesBackgroundFillStyle(new SolidFill({ color: ColorRGBA(0, 0, 0, 100) }))
Object itself
FillStyle or function which mutates the active FillStyle.
Set LineStyle of series background border stroke.
// Example usage,
ChartXY.setSeriesBackgroundStrokeStyle(new SolidLine({
thickness: 2,
fillStyle: new SolidFill({ color: ColorRGBA( 0, 255, 0 ) })
}))
Related API:
Object itself
LineStyle or function which mutates the active LineStyle.
Set the state for all Series in the Chart to highlight on mouse hover.
Object itself for fluent interface.
True if all Series should be highlighted on mouse hover, false if not.
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 Chart Title.
Example usage:
// Create a new style
Chart.setTitleFillStyle(new SolidFill({ color: ColorHEX('#F00') }))
// Change transparency
Chart.setTitleFillStyle((solidFill) => solidFill.setA(80))
// Set hidden
Chart.setTitleFillStyle(emptyFill)
Chart itself
Either a FillStyle object or a function, which will be used to create a new FillStyle based on current value.
Set font of Chart Title.
Example usage:
// Create a new FontSettings
Chart.setTitleFont(new FontSettings({ size: 24, style: 'italic' }))
// Change existing settings
Chart.setTitleFont((fontSettings) => fontSettings.setWeight('bold'))
Chart itself
Either a FontSettings object or a function, which will be used to create a new FontSettings based on current value.
Specifies padding after chart title.
This does not have an effect if title is hidden (empty FillStyle).
// Example 1, specify vertical margins
ChartXY.setTitleMargin({ top: 0, bottom: 10 })
// Example 2, specify margins for all sides with same value for Title.
ChartXY.setTitleMargin(40)
Chart itself for fluent interface
Gap after the chart title in pixels.
Beta
Not to be confused with GlowEffect
Introduced in v7.0. API may be changed according to user feedback and reports.
Beta
Configure user interactions from a set of preset options.
Without any explicit configuration, the charts select the default user interaction scheme based on available information, such as axis types, attached series and data supplied to series.
The setUserInteraction methods allow explicitly configuring the used interaction scheme.
This is not a definitive operation, but rather modifies the current state.
For example, modifying pan interaction does not affect the state of any other interactions.
// Example, disable all user interactions
chart.setUserInteractions(undefined)
// Example, enable camera zoom on mouse wheel
chart.setUserInteractions({
zoom: {
wheel: {
camera: true,
},
},
})
// Example, restore default interactions
chart.setUserInteractions({})
Object itself.
Introduced in v7.0.0. API may change according to user feedback.
Option with any set of properties of Chart3DUserInteractions or undefined to disable all interactions.
Translate a coordinate in HTML client coordinate system to relative coordinates within the component.
const locationClient = { clientX: document.body.clientWidth * 0.2, clientY: document.body.clientHeight * 0.5 }
const locationRelative = chart.translateCoordinate(locationClient, chart.coordsRelative)
// locationRelative is in pixels relative to bottom left corner of the chart
Relative coordinates can be used for positioning LightningChart JS UI components:
const textBox = chart.addUIElement(UIElementBuilders.TextBox, chart.coordsRelative)
// Left bottom of TextBox is positioned 20 pixels right and 20 pixels up from charts bottom left corner
.setOrigin(UIOrigins.LeftBottom)
.setPosition({ x: 20, y: 20 })
NOTE: Currently coordinate translations can't be guaranteed to be in sync with latest updates to charts.
For example, if you change axis interval, or add data to a series, you need to wait for 1 frame to be displayed before translateCoordinate will behave as expected.
LineSeries.add(myData)
requestAnimationFrame(() => {
// translateCoordinate should now consider data added just now.
})
Translate a coordinate from relative control coordinates to HTML client coordinate system.
// 10 pixels left and 20 pixels up from controls bottom left corner
const locationRelative = { x: 10, y: 20 }
const locationClient = chart.translateCoordinate(locationRelative, chart.coordsRelative, chart.coordsClient)
Client coordinates can be used to absolute position HTML elements using CSS, for example.
myHTMLElement.style.position = 'absolute'
myHTMLElement.style.left = locationClient.clientX
myHTMLElement.style.top = locationClient.clientY
NOTE: Currently coordinate translations can't be guaranteed to be in sync with latest updates to charts.
For example, if you change axis interval, or add data to a series, you need to wait for 1 frame to be displayed before translateCoordinate will behave as expected.
LineSeries.add(myData)
requestAnimationFrame(() => {
// translateCoordinate should now consider data added just now.
})
Translate x, y, z coordinates between different 3D coordinate systems and HTML client coordinate system.
// Example, translate coordinate from Chart3D Axes to World Space.
const coordWorld = Chart3D.translateCoordinate(
// Coordinate on Axes.
{ x: 10, y: 5, z: 25 },
// Source coordinate system.
chart3D.coordsAxis,
// Target coordinate system.
chart3D.coordsWorld
)
// Example, translate coordinate from Chart3D Axes to HTML client coordinate system.
const locClient = Chart3D.translateCoordinate(
// Coordinate on Axes.
{ x: 10, y: 5, z: 25 },
// Source coordinate system.
chart3D.coordsAxis,
// Target coordinate system.
chart3D.coordClient
)
NOTE: Currently coordinate translations can't be guaranteed to be in sync with latest updates to charts.
For example, if you change axis interval, or add data to a series, you need to wait for 1 frame to be displayed before translateCoordinate will behave as expected.
LineSeries.add(myData)
requestAnimationFrame(() => {
// translateCoordinate should now consider data added just now.
})
Chart for visualizing data in a 3-dimensional scene, with camera and light source(s).
Camera can be moved around with user interactions (mouse & touch). It is always oriented to face the center of the scene.
Light source is always located at the location of the Camera, and directed towards the center of Axes.
Data can be added to the Chart via various Series types, each with their own method of visualization: