LinechartLayout Class
Assembly: Qlik.Sense.Client.dll
Inheritance
-
System.Object
-
AbstractStructure
-
GenericObjectLayout
-
VisualizationBaseLayout
- LinechartLayout
-
VisualizationBaseLayout
-
GenericObjectLayout
-
AbstractStructure
Syntax
public class LinechartLayout : VisualizationBaseLayout, IDisposable, ILinechartLayout, IVisualizationBaseLayout, IGenericObjectLayout, IAbstractStructureConstructors
| Name | Description |
|---|---|
| LinechartLayout() |
Creates an instance of the LinechartLayout class |
Properties
| Name | Description |
|---|---|
| Color |
Color settings. JSON property name: color |
| DataPoint |
Data point settings. JSON property name: dataPoint |
| DimensionAxis |
Dimension axis settings. JSON property name: dimensionAxis |
| GridLine |
Grid lines settings. JSON property name: gridLine |
| HyperCube |
JSON property name: qHyperCube |
| Legend |
Legend settings. JSON property name: legend |
| LineType |
Type of line chart. JSON property name: lineType |
| MeasureAxis |
Line chart measure axis settings. JSON property name: measureAxis |
| NullMode |
Null value presentation. JSON property name: nullMode |
| PreferContinuousAxis |
Chart axis setting to control preference of scale on a dimensional axis. If true, the scale along the dimensional axis will be continuous if the data supports it, discrete otherwise. JSON property name: preferContinuousAxis |
| RefLine |
JSON property name: refLine |
| ScrollStartPos |
Scroll Alignment. If 0, then the scrollbar will start at the left/top of the chart, if 1 it starts at the right/bottom of the chart. Generally decides if the scroll starts at the beginning or end of the data JSON property name: scrollStartPos |
| SeparateStacking |
Stack positive and negative values separately. Dependent of lineType property. JSON property name: separateStacking |
| StackedArea |
Stack areas. Dependent of lineType property. JSON property name: stackedArea |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!