VTK/Charts/ChartAPI: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
mNo edit summary |
mNo edit summary |
||
| Line 28: | Line 28: | ||
vtkChartPie | vtkChartPie | ||
vtkMapper | |||
vtkChartMapper | |||
vtkPlot | vtkPlot | ||
vtkPlotLine | vtkPlotLine | ||
| Line 48: | Line 50: | ||
] | ] | ||
vtkProp -> vtkChart | vtkProp -> vtkChart | ||
vtkMapper -> vtkChartMapper | |||
vtkChartMapper -> vtkPlot | |||
vtkChart -> vtkChartXY | vtkChart -> vtkChartXY | ||
Revision as of 20:08, 21 October 2009
The diagram below shows the basic relationship between the different classes that make up a chart. For clarity only the composition of a vtkChartXY is shown, but all charts have multiple components used to draw their parts. Each component class that has something rendered to the screen has a function with the following prototype,
<source lang="cpp">bool Paint(vtk2DPainter *painter);</source>
These member functions are called by the chart's RenderOverlay function. The chart manages the order in which the Paint functions are called, and so the grid would be drawn over by the plots, and they in turn would be drawn over by the axes and text.
