If an instance of this class is part of a Feature that has been inserted into a MemoryDataSet then you must use the Guard class to lock the dataset that the feature belongs to before you read or modifiy the state of the VectorGeometry. Exceptions to this rule are noted on the documentation page for each individual member.

More information about thread safety of objects in a dataset can be found in Threading Model, datasets and features.

If an instance of this class is part of a Feature that has been inserted into a MemoryDataSet then you must use the Guard class to lock the dataset that the feature belongs to before you read or modifiy the state of the VectorGeometry. Exceptions to this rule are noted on the documentation page for each individual member.

More information about thread safety of objects in a dataset can be found in Threading Model, datasets and features.

If an instance of this class is part of a Feature that has been inserted into a MemoryDataSet then you must use the Guard class to lock the dataset that the feature belongs to before you read or modifiy the state of the VectorGeometry. Exceptions to this rule are noted on the documentation page for each individual member.

More information about thread safety of objects in a dataset can be found in Threading Model, datasets and features.

If an instance of this class is part of a Feature that has been inserted into a MemoryDataSet then you must use the Guard class to lock the dataset that the feature belongs to before you read or modifiy the state of the VectorGeometry. Exceptions to this rule are noted on the documentation page for each individual member.

More information about thread safety of objects in a dataset can be found in Threading Model, datasets and features.