JaggedData

Purpose

This property controls whether Subsets can contain varying quantity of Points per Subset.  Mostly for Pesgo and Pepso (RenderEngine=Direct2D) as Pe3do Direct3D + ComputeShader expects non-jagged data.  Direct2D is the common use of JaggedData. Pe3do and not using ComputeShader for PolyMode = Scatter and Line or Point PlottingMethod may be one case to try for Pe3do but filling uneven data with NullData is the legacy and proven approach. 

Comments

Historically, prior to Version10, ProEssentials had a limitation that Subsets needed to be the same quantity for all Points. Thus memory was always one contiguous block of memory for all Subsets and Points.  For 98% of charts this is fine and ideal. And GraphAnnotations and or null data was used in cases to work around this limitation. 

With JaggedData set to True, ProEssentials can optionally work with Subsets as individual blocks of memory per Subset. One does not need to set the Points property.  When the chart is told to initialize via PEreinitialize, Points will be set to the maximum of any one Subset. 

*Note, JaggedData is a new feature and data handling is a very large scope topic, so JaggedData does have current limitations in the types of charts, PlottingMethods, and RenderEngines. For now, JaggedData is limited to RenderEngine = Direct2D and the Scientific Graph and PolarSmith controls. As ProEssentials evolves, JaggedData will support more use-cases. 

The demo examples 142, 143, and 144 show implementations of JaggedData via spoon feeding, passed by a CopyFrom method, and not passed but identified by pointer to local memory.

PeData.JaggedData members of Pesgo.PeData, Pepso.PeData 

See Also: YData, XData