GitLab

The polygon-model feature size is now set as a fraction of the
bounds of the file being imported.

Yumin Yuan authored Jan 20, 2016 and David Thompson committed Mar 15, 2016

The new Import operator will use vtk readers to read files like shape, poly, vtk or vtp, map files etc, then invoke CreateEdge operatorusing point coordinates of line cells from reader-output-polydata as input, to create edges for a new empty polygon model.

Yumin Yuan authored Jan 20, 2016 and David Thompson committed Mar 15, 2016

In this commit, a new vtkCMBPolygonModelImporter class is also added. This class is
just a wrapper around vtkGDALVectorReader to output a polydata.

Yumin Yuan authored Jan 19, 2016 and David Thompson committed Mar 15, 2016

The readers and meshing classes in discrete session are really not related to discrete models. So moving those classes into common vtk extension will allow other session to use them, for example, the polygon session can use the readers to import shape files and build polygon models. The original files in vtk extension are mostly for model and mesh sources, so they are put in a new folder (source) under vtk extension.

Ben Boeckel authored Mar 02, 2016 and David Thompson committed Mar 15, 2016

The plugins and Python libraries were not getting this set properly.
Instead of setting the property manually on all of the targets, set the
default value using the CMAKE_INSTALL_NAME_DIR variable.

Ben Boeckel authored Feb 24, 2016 and David Thompson committed Mar 15, 2016

Rather than requiring post-processing to remove logic, add a CMake
variable which can be set to disable to relevant code from the install
tree if bootstrapping is not necessary.

Ben Boeckel authored Feb 23, 2016 and David Thompson committed Mar 15, 2016

Windows to the rescue.

Ben Boeckel authored Feb 23, 2016 and David Thompson committed Mar 15, 2016

Remus now ships a proper configuration file.

+ The precision was not high enough to prevent overflow.
+ The new logic is much simpler (and horked from the face-creation logic).
+ The polygonForceCreateFace test now exercises this implementation.

Multiple construction methods.
Also, add smtkSuperclassMacro to polygon operators.
Add some auxiliary methods to help with transcription and edge creation
from within "force create face".

Now loops and uses should be set up properly.
Also, the model has references to any edges involved in the face
removed (as free cells) and the face added (as a free cell) so that
the subphrase generator displays the model hierarchy correctly.

... where point coordinates are repeated (by skipping the
copies). Also, make holes in the test face concave.

This adds a new operator that adds a face given a sequence
of points defining the outer loop and optionally additional
points specifying inner loops.
The edge(s) and face are both created by the operator without sanity checks.
The tessellation is obtained by constructing a boost polygon and querying
it for trapezoids which are turned into a triangle fan (for various reasons).

This fixes the issue with the extended test case which had a non-simple hole.
The problem turned out not to be the complexity of the hole but rather the
angle tests used to insert fragments into a ring around the current sweep point;
when the CCW angle swept between successive fragments was large (> pi), then the
cross-product test failed to recognize that a fragment could be inserted.

The test for whether a segment has been flipped must use
extended-precision coordinates to avoid integer overflow.

Always verify that map entries exist before accessing the shared
pointer held by the map.

Some utility methods for creating SMTK entity records in common arrangemnts.

Track regions not connected by edges but by the sweepline.

Disconnected regions and loops are correctly detected.
Disjoint regions are not merged together; that requires
additional work.

The one needed for the polygon branch is the preview entity,
which is used to hold tessellation information for visual feedback
during a geometric operation.

+ Preview entities may be related to model and/or mesh entities;
+ they may have text notes attached to them to be shown on mouse-hover
  or in a list that is tied to rendering (so that brushing the list
  highlights the preview geometry and vice-versa);
+ they may be associated with attributes, but there is not a use case for this yet;
+ they may have properties associated with them indicating that one
  of several preview entities should be selected to disambiguate an
  operation.