Skip to content

Resolve "The ImageDataToUniformGrid filter for composite datasets should only be available in the GUI if there is a vtkImageData in the composite dataset"

Cory Quammenrequested to merge
cory.quammen/paraview:19357-contains-dataset-domain into master

Add child data type domain matching options for composite data

vtkSMDataTypeDomain can now qualify matches to input composite data based on three criteria:

  • any child data matches any of a set of data types
  • all child data match any of a set of data types
  • child data types do not matter

XML for vtkSMDataTypeDomain has been augmented to support these options.

DataType children of the DataTypeDomain XML element that has a "value" attribute specifying a composite data type now may have an optional attribute called "child_match". If the "child_match" attribute is omitted, then child types are ignored. If specified, the "child_match" attribute can have two possible values, "any" and "all".

  • "any" means that if any of the child data types match listed types, then the composite dataset is in the domain.

  • "all" means that if all child data types match the listed types, then the composite dataset is in the domain.

Child DataType elements can be added under the composite DataType to specify the valid types of child data objects.

For example,

<DataTypeDomain name="input_type">
  <DataType value="vtkImageData" />
  <DataType value="vtkCompositeDataSet" block_match="any">
    <DataType value="vtkImageData" />
  </DataType>
</DataTypeDomain>

specifies that vtkImageData and vtkCompositeDataSets that have any vtkImageData blocks are in the domain. If the "child_match" attribute were set to "all" instead, then all blocks would need to be vtkImageData for the vtkCompositeDataSet to be in the domain. If "child_match" is omitted, then any DataType child elements are ignored.

Closes #19357 (closed)

Edited by Cory Quammen

Merge request reports