GitLab

ParaView's selection-handling rewrites the VTK selection created
during pick events, dropping information that SMTK needs to recover
component IDs. To address this, ParaView has moved its rewrite
logic into a new class, named `vtkPVEncodeSelectionForServers`,
which applications (or plugins) can override using the vtkObjectFactory.

SMTK now overrides creation of this class, returning a custom subclass
named `vtkSMTKEncodeSelection`. This class is created on the client
and dispatches ParaView selections to operations in a new group
(VTKSelectionRespondersGroup). These operations are provided access
to the client-side SMTK selection instance and the first operation
to process a given resource is accepted as the selection updater
for that resource.

This commit also adds a toolbar filter-option for selecting instance
entities and an icon for instances in the resource browser widget.

Replace ::moab::Range with boost's interval_set and remove all moab
API from smtk::mesh core.

Since data members should start with a m_ you no longer need to refre to them
via the this pointer so this->m_foo is now just m_foo

Introduce smtk::mesh::DataSet, which provides the ability to assign to
the cells and points of meshsets double-valued data of user-defined
tuple length. Change InterpolateMeshElevation operator to
InterpolateMesh and change its functionality from modifying the
z-coordinate of a mesh's points to adding interpolated data to a
meshset's cells or points according to the mesh's centroid. Augment
ImportVTKData andExportVTKData to accept and create double-valued VTK
cell data, respectively.

This allows the robot to enforce formatting and fix formatting issues
automatically.

Currently smtk::mesh::PointLocator is a point to point locator with only the
ability to find all points within a spherical radius.

Previously you could only fetch the coordinates of a point set. Now you can
also modify the coordinates of a point set.

The modified flag for a mesh collection represents that underlying mesh
database representation has changed such that a write would generate a file
that would not be byte equivalent to the input file.

In the case of mesh databases that are generated in-memory, the modified
flag is set to be true once the first mesh element is added to the database.

Now when you are iterating the cells with for_each you get the Handle id
for the current cell.

Previously a smtk::mesh::Collection would only store the association
to a model in a member variable, and not inside the backend interface.
Now with these changes we have added support for the backend interface
to hold the model uuid that we are associated too.

This means that once a collection is stored to disk, loading back the collection
will restore all the proper relationships to the model.