Gigasoft.ProEssentials.Pesgo.PeData Members

This property is for transferring new XData into a Scientific Graph Object which is being used in a real-time implementation. Existing XData will first be shifted to make room for the newest data if CircularBuffers is False.

This property is for transferring new XData into a graph which is being used in a real-time implementation. Existing XData will first be shifted to make room for the newest data if CircularBuffers is False.

This property is for transferring new YData into a graph which is being used in a real-time implementation. Existing YData will first be shifted to make room for the newest data if CircularBuffers is False.

This property is for transferring new YData into a graph which is being used in a real-time implementation. Existing YData will first be shifted to make room for the newest data if CircularBuffers is False.

This property is only needed in a real-time implementation. It controls whether the graph automatically scrolls left or right. In reality, this property controls all of the append type properties like AppendYData.

This property controls whether the ProEssentials will automatically scale data that is very small or very large. What we mean by scale is reduce or enlarge all data by 10, 100, 1000, 10000 and so on. The scale factor is stored in a properties like ScaleForYData.

Set to True to enable CircularBuffers within data property arrays such as YData, XData, ZData. CircularBuffers are used with ProEssentials' AppendYData and similar features used in partial-data updating real-time use-cases.

Set to True to enable GPU side Direct3D chart construction for Direct3D RenderEngine.

DateTime mode for the Scientific Graph now support milliseconds. Major grid lines now go down to 1 millisecond rather than 1 second. This property should be set to TRUE to enable data prompts and exported data to show the millisecond portion of time.

Set to TRUE so that date/time type XData exported from the text export dialog contains seconds information.

Related to XData and used within 3D charts, 2D Contours, or any 2D Pesgo Pepso chart where all subsets or points use identical XData. Providing a method of reducing data redundancy in constructing chart.

Related to YData and used within any chart where all subsets or points use identical YData. Providing a method of reducing data redundancy in constructing chart.

Related to ZData and used within 3D charts, 2D Contours where all subsets use identical ZData. Providing a method of reducing data redundancy in constructing chart.

Set to true when RenderEngine = Direct3D and a real-time implementation will need to incrementally change data. Used in conjunction with properties RealTimeStartingIndex, RealTimeQuantity.

Used to set the daily end time when used in conjunction with SpecialDateTimeMode, StartTime, and DateTimeMode.

Gets and Sets data reduction strength. Default=Quality. Setting to fastest setting could possibly degrade for scatter type charts but actually should be fine for most charts drawn left to right.

Used with RenderEngine = Direct3D and ComputeShader = True to enable a ComputeShader and parallelism to pre-filter 2D line data prior to sending to the final ComputeShader that uses parallelism to construct the scene.

Read only. True if image is a product of data reduction. PeData.Filter2D or PeData.Filter3D and Subsets/Points and size of chart all effect if FilterOn is True.

This property controls whether Subsets can contain varying quantity of Points per Subset.

This property defines the value which is designated as NULL for the y data set. Plotting method graphics, tables, and mathematical calculations will ignore NULL data values.

This property defines the x axis value which is designated as NULL. Plotting method graphics, tables, and mathematical calculations will ignore NULL data values.

This property defines the z axis value which is designated as NULL. Plotting method graphics will ignore NULL data values. The Pesgo controls use Z Data for contour and bubble plots.

This property represents the number of points per subset that the object will contain. For example, if a line chart has 3 lines, red, green, and blue, then the graph sets the Subsets property to 3.

This property controls the number of decimal positions that will be used in outputting data to object Cursor Prompt, Tables, Data Labels, and the Clipboard.

This property controls which point information is graphed when PointsToGraphVersion is equal to PEPTGV_RANDOM.

You fill this array with zero based subset indices of those subsets you wish to include in the image. The order of subset indices can optionally control the order of how subsets are drawn. This property is also related to the ScrollingSubsets property.

With the introduction of new ComputeShader logic, this feature might be less useful. Used when RenderEngine = Direct3D and DynamicBuffers set to True.

Used when RenderEngine = Direct3D and DynamicBuffers set to True. Within the chart update event/timer logic, the developer will set this property to coincide with the new data indices updated. See example 138 in the demo/example project.

Related to RenderEngine = Direct3D and ComputeShader = True, enables a more efficient path handling Direct3D buffers as part of construction of chart. Set True if XData has not changed as part of a real-time or continuously updating charting scenario/implementation.

Related to RenderEngine = Direct3D and ComputeShader = True, enables a more efficient path handling Direct3D buffers as part of construction of chart. Set True if YData has not changed as part of a real-time or continuously updating charting scenario/implementation.

Related to RenderEngine = Direct3D and ComputeShader = True, enables a more efficient path handling Direct3D buffers as part of construction of chart. Set True if ZData has not changed as part of a real-time or continuously updating charting scenario/implementation.

This property provides the right Y axis comparison subset scaling.

This property is used to determine the objects XData current amount of scaling.

This property is used to determine the objects XData current amount of scaling.

This property is used to determine the objects YData current amount of scaling.

Gets and Sets if data can potentially be optimized. Default=Auto. This setting can be used to disable or force filtering. Most likely you may need to disable in some rare types of implementations.

Gets and Sets if data can potentially be optimized. Default=Auto. This setting can be used to disable or force filtering. Sequential data in y direction is mostly used in 2d contours, and 3d surfaces 3d contours. X data is most commonly optimized.

SpecialDateTime mode produces a date/time x axis scale which only shows time between StartTime and EndTime. This produces a discontinuous x axis scale which is only continuous between certain time ranges.

By default speed improving logic is being used. You can revert to standard logic by setting this property to 1. You can use a larger value such as 20 or 50 but some image degradation may result.

Used with RenderEngine = Direct3D to enable an efficient pipeline for updating data from the cpu-side to gpu-side. Set True if repeatedly changing XData as part of a real-time updating scenario/implementation.

Used with RenderEngine = Direct3D to enable an efficient pipeline for updating data from the cpu-side to gpu-side. Set True if repeatedly changing YData as part of a real-time updating scenario/implementation.

Used with RenderEngine = Direct3D to enable an efficient pipeline for updating data from the cpu-side to gpu-side. Set True if repeatedly changing ZData as part of a real-time updating scenario/implementation.

For the Graph Object, this sets the starting date and daily start time when used in conjunction with DateTimeMode, AutoXData, DeltaX, and DeltasPerDay. It is important that this value include the date value along with time.

This property controls how two dimensional property arrays (example, YData, XData) are stored internally. Two dimensional arrays are really stored as a series of bytes. This property controls how that series of bytes is structured. row-major order or col-major order.

This property defines the number of subsets that the object will contain. For example, if a line chart has 3 lines, red, green, and blue, then the graph sets the Subsets property to 3. If each line is made up of 10 data points, then the graph sets the Points property to 10.

This property array makes it easier to select which subsets are visible. It also has a second optional ability to control the order of how subsets are drawn. When using this feature, set a value of 0 to 9 for each subset.

This property is used to communicate to ProEssentials that the XData property should not allocate it's own memory, but instead use the local memory address that has already been allocated to the appropriate size.

This property is used to communicate to ProEssentials that the YData property should not allocate it's own memory, but instead use the local memory address that has already been allocated to the appropriate size.

This property is used to communicate to ProEssentials that the ZData property should not allocate it's own memory, but instead use the local memory address that has already been allocated to the appropriate size.

This property controls whether single or double precision X axis data is used.

This property controls whether single or double precision Y axis data is used.

This property is used to transfer data into the object. The format of the data is defined by the SubsetByPoint property.

This property is used to transfer double precision XData into the object.

This property is used to transfer data into the object. The format of the data is defined by the SubsetByPoint property.

This property is used to transfer double precision data into the object.

The 3D Scientific Graph uses ZData to identify data plotted against the z axis. The Scientific Graph Object uses ZData to control bubble sizes for the Bubble plotting method.