Workspace 6.21.5
|
Template for instantiating data factories for a particular type. More...
#include <Workspace/DataExecution/DataObjects/typeddatafactory.h>
Static Public Member Functions | |
static void | assign (const T &src, T &dest) |
static bool | canSerialize (const T &t) |
static T * | clone (const T &t) |
static T * | create () |
static void | destroy (T *t) |
static const T * | getData (const DataObject &obj) |
static T * | getData (DataObject &obj) |
static bool | load (const SerializedItem &item, T &t) |
static bool | save (SerializedItem &item, const T &t) |
static void | setData (DataObject &obj, T *data, bool ownsData) |
Instantiate this for each type T you want to make available to the workspace. If you need special behaviour for any of the virtual functions, you can provide your own specialisations for your particular type T. The workspace makes no direct use of this template itself (it does everything through the base class), and only the workspace should be calling any of the virtual functions. In other words, you are allowed to override the virtual functions, but you aren't allowed to call them yourself.
You should read the comments for DataFactory for any function you specialize, as there are some assumptions and pre-conditions that must be satisfied in some cases.
Client code should never call functions in this class directly. Rather, use the DataFactoryTraits class instead. Client code will, however, sometimes provide specializations of TypedDataFactory member functions, but this would not by typical.
|
inlinestatic |
src | Source object to copy. |
dest | Destination object to assign to. |
This is analogous to an object's assignment operator.
|
inlineoverridevirtual |
src | The source object to copy. |
dest | The destination object to assign to. |
If assignment is not supported by this data type, then a call to this function normally does nothing. Callers should check the result of isAssignable() before using this function.
Implements DataFactory.
bool canSerialize | ( | const QByteArray & | q | ) |
bool canSerialize | ( | const QColor & | c | ) |
bool canSerialize | ( | const QDateTime & | list | ) |
bool canSerialize | ( | const QFont & | f | ) |
bool canSerialize | ( | const QJsonDocument & | q | ) |
bool canSerialize | ( | const QPointF & | f | ) |
bool canSerialize | ( | const QQuaternion & | q | ) |
bool canSerialize | ( | const QStringList & | list | ) |
bool canSerialize | ( | const QVariant & | data | ) |
bool canSerialize | ( | const QVector< QDateTime > & | dateTimes | ) |
|
inlinestatic |
t | The object to query if it can be serialized. |
The default implementation assumes that the type T can be serialized, so the function always returns true
by default. If T supports no form of serialization, provide a specialization which returns false.
RegionIntersection * clone | ( | const RegionIntersection & | t | ) |
RegionNegate * clone | ( | const RegionNegate & | t | ) |
RegionTransform * clone | ( | const RegionTransform & | t | ) |
RegionUnion * clone | ( | const RegionUnion & | t | ) |
|
inlinestatic |
t | A pointer to an object assumed to be of the same type as this factory, or a subclass of that type. If the factory provides a specialisation for this function, it must obey this substitutability principle. |
This is analogous to an object's copy constructor or to the cloning design pattern. It can be implemented either way.
|
inlineoverridevirtual |
obj | The object to clone. |
The subclass implementation must check if obj is of the same type as what the factory manages. If it is not, it must forward the call to obj's data factory.
Implements DataFactory.
|
inlineoverridevirtual |
lhs | The first operand |
rhs | The second operand |
If comparison is not supported by this data type, then a call to this function is guaranteed to return false.
Implements DataFactory.
|
inlineoverridevirtual |
lhs | The first operand |
rhs | The second operand |
relationOut | The identified relationship between the two objects. If the return value is true (i.e. the items are the same), relationOut will be 0. If the return value is false, relationOut will be -1 if lhs < rhs, and 1 if lhs > rhs. |
If sorting is not supported by this data type, then a call to this function is guaranteed to return false.
Implements DataFactory.
DataAnalysis::Array3d * create | ( | ) |
Array3d is an abstract base class, but it is clonable and has a sensible default subclass, Array3dNull.
DataAnalysis::Array3dScalar * create | ( | ) |
Array3dTyped<double> is an abstract base class, but it is clonable and has a sensible default subclass, Array3dNullTyped<double>. Therefore, a request to create a Array3dTyped<double> instance will actually create a Array3dNullTyped<double>.
DataAnalysis::Array3dInteger * create | ( | ) |
Array3dInteger is an abstract base class, but it is clonable and has a sensible default subclass, Array3dNullInteger. Therefore, a request to create a Array3dInteger instance will actually create a Array3dNullInteger.
DataAnalysis::ArrayNd * create | ( | ) |
DataAnalysis::DataSeries * create | ( | ) |
DataSeries is an abstract base class, but it is clonable and has a sensible default subclass, NullDataSeries. Therefore, a request to create a DataSeries instance will actually create a NullDataSeries.
DataAnalysis::DataSeriesMapper * create | ( | ) |
We make the node state mapper the default node mapper. It will still be useless without setting the state name to map.
DataAnalysis::NamedDimensionRangeFilter * create | ( | ) |
DataAnalysis::SqlBoundObjectGroup * create | ( | ) |
Create an invalid object group by default.
DataAnalysis::Image3d * create | ( | ) |
Image3d is an abstract base class, but it is clonable and has a sensible default subclass, Image3dNull. Therefore, a request to create an Image3d instance will actually create a Image3dNull object.
Mesh::Array3dVector * create | ( | ) |
Array3dVector is an abstract base class, but it is clonable and has a sensible default subclass, Array3dNullVector. Therefore, a request to create a Array3dVector instance will actually create a Array3dNullVector.
Mesh::ElementMapper * create | ( | ) |
We make the element state mapper the default element mapper. It will still be useless without setting the state name to map.
Mesh::MeshModelFilter * create | ( | ) |
Mesh::MeshModelInterface * create | ( | ) |
When a data factory wants to create a MeshModelInterface, we provide a default concrete class of type StreamlinedMeshModelInterface.
Mesh::NodeMapper * create | ( | ) |
We make the node state mapper the default node mapper. It will still be useless without setting the state name to map.
Mesh::VectorNodeMapper * create | ( | ) |
We make the node state mapper the default node mapper. It will still be useless without setting the state name to map.
ElementCriterion * create | ( | ) |
ElementCriterion is an abstract base class, but it is clonable and has a sensible default subclass, ElementCriterionAllPass. Therefore, a request to create a ElementCriterion instance will actually create a ElementCriterionAllPass.
NodeCriterion * create | ( | ) |
NodeCriterion is an abstract base class, but it is clonable and has a sensible default subclass, NodeCriterionAllPass. Therefore, a request to create a NodeCriterion instance will actually create a NodeCriterionAllPass.
Region * create | ( | ) |
Object group is an abstract base class, but it is clonable and has a sensible default subclass, BoundingBox. Therefore, a request to create a Region instance will actually create a BoundingBox.
PackageItem * create | ( | ) |
Light * create | ( | ) |
Light is an abstract base class. To allow creation of a Light where one is really needed, we create an ambient light since it is a sensible subclass which doesn't actually add any more data to the light and will at least make scene items more or less visible.
Glypher * create | ( | ) |
MeshModelAppearance is an abstract base class, but it is clonable and has a sensible default subclass, DefaultAppearance. Therefore, a request to create a MeshModelAppearance instance will actually create a DefaultAppearance object. Note, however, that the DefaultAppearance class is not added as a workspace data type, so you cannot create an instance of it any other way.
Texturizer * create | ( | ) |
Rendering::SceneItem * create | ( | ) |
SceneItem is an abstract base class. To allow creation of a SceneItem where one is really needed, we create an empty Transform object since it is a sensible subclass which doesn't actually add anything physical to a scene.
Rendering::Shader * create | ( | ) |
Shader is an abstract base class, but it is clonable and has a sensible default subclass, NullShader.
ObjectGroup * create | ( | ) |
Object group is an abstract base class, but it is clonable and has a sensible default subclass, EmptyGroup. Therefore, a request to create an ObjectGroup instance will actually create an EmptyGroup.
|
inlinestatic |
This is analogous to the new
operator, but the factory is free to implement it however it wishes as long as the clone() and destroy() functions it provides are compatible. The one restriction is that the object should be properly initialised. The create() function for all types should generally try to follow this guideline wherever possible.
The default implementation is to create a new object using the default constructor for T using the new
operator. For built-in C++ types (also known as POD types), the initialising form of the default constructor is used to ensure that the object returned does not have an undefined value (it will typically hold zero for POD types).
Provenance::ProvenanceReporter::Reporter * create | ( | ) |
|
inlineoverridevirtual |
delete
operator. Implements DataFactory.
|
inlinestatic |
t | The object to destroy, assumed to be created through a call to this factory's create or clone functions. |
delete
command.This is analogous to the delete
operator, and indeed this is the default implementation of the function.
|
inlineoverridevirtual |
obj | The DataObject to delete. It must have been created by a call to createDataObject() with this factory. |
delete
command. Implements DataFactory.
|
inlinestatic |
This is an overloaded member function, provided for convenience. It differs from the above function only in what argument(s) it accepts.
|
inlinestatic |
obj | The object whose underlying data should be returned. |
A check is performed as to whether the data factory for obj is indeed this factory. If it is not then the function returns nullptr.
|
inlineoverridevirtual |
map | Map object that maps enum values to enum names. |
Implements DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
overridevirtual |
Implements DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
virtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
overridevirtual |
If a data type is defined by a third party library, it is possible the type may be added to Workspace by different plugins. Workspace may generate adaptor between them as long as they provide a non-empty identical string and the name of the type are identical as well. Recommend to use the name of third party library with it's version name to make them compatible.
Reimplemented from DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
virtual |
Implements DataFactory.
|
overridevirtual |
Implements DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
|
inlineoverridevirtual |
Implements DataFactory.
bool load | ( | const SerializedItem & | item, |
QColor & | c | ||
) |
bool load | ( | const SerializedItem & | item, |
QDateTime & | list | ||
) |
bool load | ( | const SerializedItem & | item, |
QFont & | f | ||
) |
bool load | ( | const SerializedItem & | item, |
QJsonDocument & | data | ||
) |
bool load | ( | const SerializedItem & | item, |
QPointF & | f | ||
) |
bool load | ( | const SerializedItem & | item, |
QQuaternion & | q | ||
) |
bool load | ( | const SerializedItem & | item, |
QStringList & | list | ||
) |
bool load | ( | const SerializedItem & | item, |
QVariant & | data | ||
) |
bool load | ( | const SerializedItem & | item, |
QVector< QDateTime > & | dateTimes | ||
) |
|
inlinestatic |
item | Holds the data to be loaded into the object. |
t | The object to be updated with the loaded data. |
|
inline |
|
inline |
|
inline |
bool save | ( | SerializedItem & | item, |
const QColor & | c | ||
) |
bool save | ( | SerializedItem & | item, |
const QDateTime & | list | ||
) |
bool save | ( | SerializedItem & | item, |
const QFont & | f | ||
) |
bool save | ( | SerializedItem & | item, |
const QJsonDocument & | data | ||
) |
bool save | ( | SerializedItem & | item, |
const QPointF & | f | ||
) |
bool save | ( | SerializedItem & | item, |
const QQuaternion & | q | ||
) |
bool save | ( | SerializedItem & | item, |
const QStringList & | list | ||
) |
bool save | ( | SerializedItem & | item, |
const QVariant & | data | ||
) |
bool save | ( | SerializedItem & | item, |
const QVector< QDateTime > & | dateTimes | ||
) |
|
inlinestatic |
item | Where the data for the object should be stored. |
t | The object whose data should be stored. |
|
inlinestatic |
obj | The target data object whose underlying data should be set. It must be of real type TypedObject<T> (this is only tested in debug mode by an assertion). |
data | The actual data to use for obj. It can be a pointer to type T or any class derived from it. This allows subclass objects to be assigned to base data objects. The data object handling of the various templates ensures that the correct factories are used when destroying derived objects stored in this way. |
ownsData | True if obj should own the data being stored in it by this call. |
|
inlineoverridevirtual |
Implements DataFactory.