| abstractitemmodelhandler.cpp |
|
7640 |
- |
| abstractitemmodelhandler_p.h |
|
2567 |
- |
| abstractrenderitem.cpp |
|
430 |
- |
| abstractrenderitem_p.h |
|
1419 |
- |
| baritemmodelhandler.cpp |
|
12223 |
- |
| baritemmodelhandler_p.h |
|
1354 |
- |
| barrenderitem.cpp |
|
1589 |
- |
| barrenderitem_p.h |
|
2137 |
- |
| customrenderitem.cpp |
|
2762 |
- |
| customrenderitem_p.h |
|
8057 |
- |
| labelitem.cpp |
|
869 |
- |
| labelitem_p.h |
|
842 |
- |
| qabstract3dseries.cpp |
!
\class QAbstract3DSeries
\inmodule QtDataVisualization
\brief The QAbstract3DSeries class is a base class for all data series.
\since QtDataVisualization 1.0
There are inherited classes for each supported series type: QBar3DSeries,
QScatter3DSeries, and QSurface3DSeries.
For more information, see \l{Qt Data Visualization Data Handling}.
|
24389 |
- |
| qabstract3dseries.h |
|
5805 |
- |
| qabstract3dseries_p.h |
|
4947 |
- |
| qabstractdataproxy.cpp |
!
\class QAbstractDataProxy
\inmodule QtDataVisualization
\brief The QAbstractDataProxy class is a base class for all data
visualization data proxies.
\since QtDataVisualization 1.0
The following visualization type specific inherited classes are used instead
of the base class: QBarDataProxy, QScatterDataProxy, and QSurfaceDataProxy.
For more information, see \l{Qt Data Visualization Data Handling}.
|
2486 |
- |
| qabstractdataproxy.h |
|
1026 |
- |
| qabstractdataproxy_p.h |
|
1065 |
- |
| qbar3dseries.cpp |
!
\class QBar3DSeries
\inmodule QtDataVisualization
\brief The QBar3DSeries class represents a data series in a 3D bar graph.
\since QtDataVisualization 1.0
This class manages the series specific visual elements, as well as the series
data (via a data proxy).
If no data proxy is set explicitly for the series, the series creates a default
proxy. Setting another proxy will destroy the existing proxy and all data added to it.
QBar3DSeries supports the following format tags for QAbstract3DSeries::setItemLabelFormat():
\table
\row
\li @rowTitle \li Title from row axis
\row
\li @colTitle \li Title from column axis
\row
\li @valueTitle \li Title from value axis
\row
\li @rowIdx \li Visible row index. Localized using the graph locale.
\row
\li @colIdx \li Visible column index. Localized using the graph locale.
\row
\li @rowLabel \li Label from row axis
\row
\li @colLabel \li Label from column axis
\row
\li @valueLabel \li Item value formatted using the format of the value
axis attached to the graph. For more information,
see \l{QValue3DAxis::labelFormat}.
\row
\li @seriesName \li Name of the series
\row
\li %<format spec> \li Item value in the specified format. Formatted
using the same rules as \l{QValue3DAxis::labelFormat}.
\endtable
For example:
\snippet doc_src_qtdatavisualization.cpp 1
\sa {Qt Data Visualization Data Handling}, QAbstract3DGraph::locale
|
15089 |
- |
| qbar3dseries.h |
|
1813 |
- |
| qbar3dseries_p.h |
|
1225 |
- |
| qbardataitem.cpp |
!
\class QBarDataItem
\inmodule QtDataVisualization
\brief The QBarDataItem class provides a container for resolved data to be added to bar graphs.
\since QtDataVisualization 1.0
A bar data item holds the data for a single rendered bar in a graph.
Bar data proxies parse data into QBarDataItem instances for visualization.
\sa QBarDataProxy, {Qt Data Visualization C++ Classes}
|
2277 |
- |
| qbardataitem.h |
|
947 |
- |
| qbardataitem_p.h |
|
637 |
- |
| qbardataproxy.cpp |
!
\class QBarDataProxy
\inmodule QtDataVisualization
\brief The QBarDataProxy class is the data proxy for a 3D bars graph.
\since QtDataVisualization 1.0
A bar data proxy handles adding, inserting, changing, and removing rows of
data.
The data array is a list of vectors (rows) of QBarDataItem instances.
Each row can contain a different number of items or even be null.
QBarDataProxy takes ownership of all QtDataVisualization::QBarDataRow objects
passed to it, whether directly or in a QtDataVisualization::QBarDataArray container.
If bar data row pointers are used to directly modify data after adding the
array to the proxy, the appropriate signal must be emitted to update the
graph.
QBarDataProxy optionally keeps track of row and column labels, which QCategory3DAxis can utilize
to show axis labels. The row and column labels are stored in a separate array from the data and
row manipulation methods provide alternate versions that do not affect the row labels.
This enables the option of having row labels that relate to the position of the data in the
array rather than the data itself.
\sa {Qt Data Visualization Data Handling}
|
23774 |
- |
| qbardataproxy.h |
|
3412 |
- |
| qbardataproxy_p.h |
|
1956 |
- |
| qcustom3ditem.cpp |
!
\class QCustom3DItem
\inmodule QtDataVisualization
\brief The QCustom3DItem class adds a custom item to a graph.
\since QtDataVisualization 1.1
A custom item has a custom mesh, position, scaling, rotation, and an optional
texture.
\sa QAbstract3DGraph::addCustomItem()
|
15657 |
- |
| qcustom3ditem.h |
|
3349 |
- |
| qcustom3ditem_p.h |
|
2057 |
- |
| qcustom3dlabel.cpp |
!
\class QCustom3DLabel
\inmodule QtDataVisualization
\brief The QCustom3DLabel class adds a custom label to a graph.
\since QtDataVisualization 1.1
The text, font, position, scaling, rotation, and colors of a custom label can
be set. In addition, the visibility of the borders and background of the
label can be toggled. Colors, borders, and background are determined by the
active theme unless set explicitly.
\note In scaling, the z-coordinate has no effect. Setting the same x- and
y-coordinates retains the original font dimensions.
\sa QAbstract3DGraph::addCustomItem()
|
9545 |
- |
| qcustom3dlabel.h |
|
2612 |
- |
| qcustom3dlabel_p.h |
|
1413 |
- |
| qcustom3dvolume.cpp |
!
\class QCustom3DVolume
\inmodule QtDataVisualization
\brief The QCustom3DVolume class adds a volume rendered object to a graph.
\since QtDataVisualization 1.2
A volume rendered
object is a box with a 3D texture. Three slice planes are supported for the volume, one along
each main axis of the volume.
Rendering volume objects is very performance intensive, especially when the volume is largely
transparent, as the contents of the volume are ray-traced. The performance scales nearly linearly
with the amount of pixels that the volume occupies on the screen, so showing the volume in a
smaller view or limiting the zoom level of the graph are easy ways to improve performance.
Similarly, the volume texture dimensions have a large impact on performance.
If the frame rate is more important than pixel-perfect rendering of the volume contents, consider
turning the high definition shader off by setting the useHighDefShader property to \c{false}.
\note Volumetric objects are only supported with orthographic projection.
\note Volumetric objects utilize 3D textures, which are not supported in OpenGL ES2 environments.
\sa QAbstract3DGraph::addCustomItem(), QAbstract3DGraph::orthoProjection, useHighDefShader
|
44815 |
- |
| qcustom3dvolume.h |
|
5754 |
- |
| qcustom3dvolume_p.h |
|
2431 |
- |
| qheightmapsurfacedataproxy.cpp |
!
\class QHeightMapSurfaceDataProxy
\inmodule QtDataVisualization
\brief Base proxy class for Q3DSurface.
\since QtDataVisualization 1.0
QHeightMapSurfaceDataProxy takes care of surface related height map data handling. It provides a
way to give a height map to be visualized as a surface plot.
Since height maps do not contain values for X or Z axes, those values need to be given
separately using minXValue, maxXValue, minZValue, and maxZValue properties. X-value corresponds
to image horizontal direction and Z-value to the vertical. Setting any of these
properties triggers asynchronous re-resolving of any existing height map.
\sa QSurfaceDataProxy, {Qt Data Visualization Data Handling}
|
24680 |
- |
| qheightmapsurfacedataproxy.h |
|
3137 |
- |
| qheightmapsurfacedataproxy_p.h |
|
1504 |
- |
| qitemmodelbardataproxy.cpp |
!
\class QItemModelBarDataProxy
\inmodule QtDataVisualization
\brief Proxy class for presenting data in item models with Q3DBars.
\since QtDataVisualization 1.0
QItemModelBarDataProxy allows you to use QAbstractItemModel derived models as a data source
for Q3DBars. It uses the defined mappings to map data from the model to rows, columns, and
values of Q3DBars graph.
The data is resolved asynchronously whenever mappings or the model changes.
QBarDataProxy::arrayReset() is emitted when the data has been resolved.
However, when useModelCategories property is set to true, single item changes are resolved
synchronously, unless the same frame also contains a change that causes the whole model to be
resolved.
Mappings can be used in the following ways:
\list
\li If useModelCategories property is set to true, this proxy will map rows and
columns of QAbstractItemModel directly to rows and columns of Q3DBars, and uses the value
returned for Qt::DisplayRole as bar value by default.
The value role to be used can be redefined if Qt::DisplayRole is not suitable.
\li For models that do not have data already neatly sorted into rows and columns, such as
QAbstractListModel based models, you can define a role from the model to map for each of row,
column and value.
\li If you do not want to include all data contained in the model, or the autogenerated rows and
columns are not ordered as you wish, you can specify which rows and columns should be included
and in which order by defining an explicit list of categories for either or both of rows and
columns.
\endlist
For example, assume that you have a custom QAbstractItemModel for storing various monthly values
related to a business.
Each item in the model has the roles "year", "month", "income", and "expenses".
You could do the following to display the data in a bar graph:
\snippet doc_src_qtdatavisualization.cpp 3
If the fields of the model do not contain the data in the exact format you need, you can specify
a search pattern regular expression and a replace rule for each role to get the value in a
format you need. For more information how the replace using regular expressions works, see
QString::replace(const QRegularExpression &rx, const QString &after) function documentation. Note that
using regular expressions has an impact on the performance, so it's more efficient to utilize
item models where doing search and replace is not necessary to get the desired values.
For example about using the search patterns in conjunction with the roles, see
\l{Simple Bar Graph} example.
\sa {Qt Data Visualization Data Handling}
|
35122 |
- |
| qitemmodelbardataproxy.h |
|
8258 |
- |
| qitemmodelbardataproxy_p.h |
|
1729 |
- |
| qitemmodelscatterdataproxy.cpp |
!
\class QItemModelScatterDataProxy
\inmodule QtDataVisualization
\brief Proxy class for presenting data in item models with Q3DScatter.
\since QtDataVisualization 1.0
QItemModelScatterDataProxy allows you to use QAbstractItemModel derived models as a data source
for Q3DScatter. It maps roles of QAbstractItemModel to the XYZ-values of Q3DScatter points.
The data is resolved asynchronously whenever the mapping or the model changes.
QScatterDataProxy::arrayReset() is emitted when the data has been resolved. However, inserts,
removes, and single data item changes after the model initialization are resolved synchronously,
unless the same frame also contains a change that causes the whole model to be resolved.
Mapping ignores rows and columns of the QAbstractItemModel and treats
all items equally. It requires the model to provide roles for the data items
that can be mapped to X, Y, and Z-values for the scatter points.
For example, assume that you have a custom QAbstractItemModel for storing various measurements
done on material samples, providing data for roles such as "density", "hardness", and
"conductivity". You could visualize these properties on a scatter graph using this proxy:
\snippet doc_src_qtdatavisualization.cpp 4
If the fields of the model do not contain the data in the exact format you need, you can specify
a search pattern regular expression and a replace rule for each role to get the value in a
format you need. For more information how the replace using regular expressions works, see
QString::replace(const QRegularExpression &rx, const QString &after) function documentation. Note that
using regular expressions has an impact on the performance, so it's more efficient to utilize
item models where doing search and replace is not necessary to get the desired values.
For example about using the search patterns in conjunction with the roles, see
ItemModelBarDataProxy usage in \l{Simple Bar Graph} example.
\sa {Qt Data Visualization Data Handling}
|
22692 |
- |
| qitemmodelscatterdataproxy.h |
|
5440 |
- |
| qitemmodelscatterdataproxy_p.h |
|
1450 |
- |
| qitemmodelsurfacedataproxy.cpp |
!
\class QItemModelSurfaceDataProxy
\inmodule QtDataVisualization
\brief Proxy class for presenting data in item models with Q3DSurface.
\since QtDataVisualization 1.0
QItemModelSurfaceDataProxy allows you to use QAbstractItemModel derived models as a data source
for Q3DSurface. It uses the defined mappings to map data from the model to rows, columns, and
surface points of Q3DSurface graph.
Data is resolved asynchronously whenever the mapping or the model changes.
QSurfaceDataProxy::arrayReset() is emitted when the data has been resolved.
However, when useModelCategories property is set to \c true, single item changes are resolved
synchronously, unless the same frame also contains a change that causes the whole model to be
resolved.
Mappings can be used in the following ways:
\list
\li If useModelCategories property is set to \c true, this proxy will map rows and
columns of QAbstractItemModel to rows and columns of Q3DSurface, and uses the value returned for
Qt::DisplayRole as Y-position by default. Row and column headers are used for Z-position and
X-position by default, if they can be converted to floats. Otherwise row and column indices
are used.
The Y-position role to be used can be redefined if Qt::DisplayRole is not suitable.
The Z-position and X-position roles to be used can be redefined if the headers or indices
are not suitable.
\li For models that do not have data already neatly sorted into rows and columns, such as
QAbstractListModel based models, you can define a role from the model to map for each of row,
column and Y-position.
\li If you do not want to include all data contained in the model, or the autogenerated rows and
columns are not ordered as you wish, you can specify which rows and columns should be included
and in which order by defining an explicit list of categories for either or both of rows and
columns.
\endlist
For example, assume that you have a custom QAbstractItemModel storing surface topography data.
Each item in the model has the roles "longitude", "latitude", and "height".
The item model already contains the data properly sorted so that longitudes and latitudes are
first encountered in correct order, which enables us to utilize the row and column category
autogeneration.
You could do the following to display the data in a surface graph:
\snippet doc_src_qtdatavisualization.cpp 5
If the fields of the model do not contain the data in the exact format you need, you can specify
a search pattern regular expression and a replace rule for each role to get the value in a
format you need. For more information how the replace using regular expressions works, see
QString::replace(const QRegularExpression &rx, const QString &after) function documentation. Note that
using regular expressions has an impact on the performance, so it's more efficient to utilize
item models where doing search and replace is not necessary to get the desired values.
For example about using the search patterns in conjunction with the roles, see
ItemModelBarDataProxy usage in \l{Simple Bar Graph} example.
\sa {Qt Data Visualization Data Handling}
|
41923 |
- |
| qitemmodelsurfacedataproxy.h |
|
9359 |
- |
| qitemmodelsurfacedataproxy_p.h |
|
1871 |
- |
| qscatter3dseries.cpp |
!
\class QScatter3DSeries
\inmodule QtDataVisualization
\brief The QScatter3DSeries class represents a data series in a 3D scatter
graph.
\since QtDataVisualization 1.0
This class manages the series specific visual elements, as well as the series
data (via a data proxy).
If no data proxy is set explicitly for the series, the series creates a default
proxy. Setting another proxy will destroy the existing proxy and all data added to it.
QScatter3DSeries supports the following format tags for QAbstract3DSeries::setItemLabelFormat():
\table
\row
\li @xTitle \li Title from x-axis
\row
\li @yTitle \li Title from y-axis
\row
\li @zTitle \li Title from z-axis
\row
\li @xLabel \li Item value formatted using the format of the x-axis.
For more information, see
\l{QValue3DAxis::setLabelFormat()}.
\row
\li @yLabel \li Item value formatted using the format of the y-axis.
For more information, see
\l{QValue3DAxis::setLabelFormat()}.
\row
\li @zLabel \li Item value formatted using the format of the z-axis.
For more information, see
\l{QValue3DAxis::setLabelFormat()}.
\row
\li @seriesName \li Name of the series
\endtable
For example:
\snippet doc_src_qtdatavisualization.cpp 1
\sa {Qt Data Visualization Data Handling}
|
12151 |
- |
| qscatter3dseries.h |
|
1622 |
- |
| qscatter3dseries_p.h |
|
1103 |
- |
| qscatterdataitem.cpp |
!
\class QScatterDataItem
\inmodule QtDataVisualization
\brief The QScatterDataItem class provides a container for resolved data to be added to scatter
graphs.
\since QtDataVisualization 1.0
A scatter data item holds the data for a single rendered item in a scatter
graph. Scatter data proxies parse data into QScatterDataItem instances for
visualization.
\sa QScatterDataProxy, {Qt Data Visualization C++ Classes}
|
3268 |
- |
| qscatterdataitem.h |
|
1533 |
- |
| qscatterdataitem_p.h |
|
661 |
- |
| qscatterdataproxy.cpp |
!
\class QScatterDataProxy
\inmodule QtDataVisualization
\brief The QScatterDataProxy class is the data proxy for 3D scatter graphs.
\since QtDataVisualization 1.0
A scatter data proxy handles adding, inserting, changing, and removing data
items.
QScatterDataProxy takes ownership of all
QtDataVisualization::QScatterDataArray and QScatterDataItem objects passed to
it.
\sa {Qt Data Visualization Data Handling}
|
11905 |
- |
| qscatterdataproxy.h |
|
2063 |
- |
| qscatterdataproxy_p.h |
|
1647 |
- |
| qsurface3dseries.cpp |
!
\class QSurface3DSeries
\inmodule QtDataVisualization
\brief The QSurface3DSeries class represents a data series in a 3D surface
graph.
\since QtDataVisualization 1.0
This class manages the series specific visual elements, as well as the series
data (via a data proxy).
If no data proxy is set explicitly for the series, the series creates a default
proxy. Setting another proxy will destroy the existing proxy and all data added to it.
The object mesh set via the QAbstract3DSeries::mesh property defines the selection
pointer shape in a surface series.
QSurface3DSeries supports the following format tags for QAbstract3DSeries::setItemLabelFormat():
\table
\row
\li @xTitle \li Title from x-axis
\row
\li @yTitle \li Title from y-axis
\row
\li @zTitle \li Title from z-axis
\row
\li @xLabel \li Item value formatted using the format of the x-axis.
For more information, see
\l{QValue3DAxis::setLabelFormat()}.
\row
\li @yLabel \li Item value formatted using the format of the y-axis.
For more information, see
\l{QValue3DAxis::setLabelFormat()}.
\row
\li @zLabel \li Item value formatted using the format of the z-axis.
For more information, see
\l{QValue3DAxis::setLabelFormat()}.
\row
\li @seriesName \li Name of the series
\endtable
For example:
\snippet doc_src_qtdatavisualization.cpp 1
\sa {Qt Data Visualization Data Handling}
|
17830 |
- |
| qsurface3dseries.h |
|
3185 |
- |
| qsurface3dseries_p.h |
|
1414 |
- |
| qsurfacedataitem.cpp |
!
\class QSurfaceDataItem
\inmodule QtDataVisualization
\brief The QSurfaceDataItem class provides a container for resolved data to be added to surface
graphs.
\since QtDataVisualization 1.0
A surface data item holds the data for a single vertex in a surface graph.
Surface data proxies parse data into QSurfaceDataItem instances for
visualization.
\sa QSurfaceDataProxy, {Qt Data Visualization C++ Classes}
|
2562 |
- |
| qsurfacedataitem.h |
|
1287 |
- |
| qsurfacedataitem_p.h |
|
661 |
- |
| qsurfacedataproxy.cpp |
!
\class QSurfaceDataProxy
\inmodule QtDataVisualization
\brief The QSurfaceDataProxy class is the data proxy for a 3D surface graph.
\since QtDataVisualization 1.0
A surface data proxy handles surface related data in rows. For this it
provides two auxiliary typedefs: QtDataVisualization::QSurfaceDataArray and
QtDataVisualization::QSurfaceDataRow. \c QSurfaceDataArray is a QList that
controls the rows. \c QSurfaceDataRow is a QList that contains
QSurfaceDataItem objects. For more information about how to feed the data to
the proxy, see the sample code in the Q3DSurface documentation.
All rows must have the same number of items.
QSurfaceDataProxy takes ownership of all \c QSurfaceDataRow objects passed to
it, whether directly or in a \c QSurfaceDataArray container.
To use surface data row pointers to directly modify data after adding the
array to the proxy, the appropriate signal must be emitted to update the
graph.
To make a sensible surface, the x-value of each successive item in all rows must be
either ascending or descending throughout the row.
Similarly, the z-value of each successive item in all columns must be either ascending or
descending throughout the column.
\note Currently only surfaces with straight rows and columns are fully supported. Any row
with items that do not have the exact same z-value or any column with items
that do not have the exact same x-value may get clipped incorrectly if the
whole surface does not completely fit within the visible x-axis or z-axis
ranges.
\note Surfaces with less than two rows or columns are not considered valid surfaces and will
not be rendered.
\note On some environments, surfaces with a lot of visible vertices may not render, because
they exceed the per-draw vertex count supported by the graphics driver.
This is mostly an issue on 32-bit and OpenGL ES2 platforms.
\sa {Qt Data Visualization Data Handling}
|
20366 |
- |
| qsurfacedataproxy.h |
|
2520 |
- |
| qsurfacedataproxy_p.h |
|
1729 |
- |
| scatteritemmodelhandler.cpp |
|
8180 |
- |
| scatteritemmodelhandler_p.h |
|
1855 |
- |
| scatterrenderitem.cpp |
|
497 |
- |
| scatterrenderitem_p.h |
|
1194 |
- |
| surfaceitemmodelhandler.cpp |
|
13336 |
- |
| surfaceitemmodelhandler_p.h |
|
1460 |
- |