mirror of
https://gitlab.kitware.com/vtk/vtk-m
synced 2024-09-16 17:22:55 +00:00
72cd0107ee
The version of `Filter::Execute` that takes a policy as an argument is now deprecated. Filters are now able to specify their own fields and types, which is often why you want to customize the policy for an execution. The other reason is that you are compiling VTK-m into some other source that uses a particular types of storage. However, there is now a mechanism in the CMake configuration to allow you to provide a header that customizes the "default" types used in filters. This is a much more convenient way to compile filters for specific types. One thing that filters were not able to do was to customize what cell sets they allowed using. This allows filters to self-select what types of cell sets they support (beyond simply just structured or unstructured). To support this, the lists `SupportedCellSets`, `SupportedStructuredCellSets`, and `SupportedUnstructuredCellSets` have been added to `Filter`. When you apply a policy to a cell set, you now have to also provide the filter. |
||
|---|---|---|
| .. | ||
| 1.3 | ||
| 1.4 | ||
| 1.5 | ||
| arrayhandlegroupvecvariable.md | ||
| binary_search_algorithms.md | ||
| ci-script.md | ||
| configurable-default-types.md | ||
| custom_portal_iterators.md | ||
| decorator_resizing.md | ||
| deprecate-execute-with-policy.md | ||
| deprecation.md | ||
| google_benchmark.md | ||
| image_io.md | ||
| io_reorganize.md | ||
| list-tag-remove-if.md | ||
| list.md | ||
| mask_and_scatters_3d_scheduling.md | ||
| readportalget.md | ||
| scoping-tokens.md | ||
| shorter-fancy-array-handle-classnames.md | ||
| std_porting_headers.md | ||
| tuple.md | ||