GitLab

+ 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.

Sessions should not have to make every operator a friend.
This adds methods to the base polygon Operator class to
provide access to the Session's storage.

Python already has a "CreateFace" function (which works for
CGM) but this commit adds "CreateFaces" for expediency in
testing the polygon session. The operators should be reconciled.

Methods like `smtk::model::Model::cellsAs<T>()` and
`smtk::model::Model::groupsAs<T>()` would append cursors
that were invalid rather than omitting values not matching
the container type. For example, calling `model->cellsAs<Edges>()`
should only return cells owned by the model that are edges
(as opposed to vertices, faces, or volumes).
Without this patch, invalid `Edge` cursors were being inserted
for each vertex, face, or volume in the model's set of cells.

Yumin Yuan authored Feb 17, 2016 and Kitware Robot committed Feb 17, 2016

043b8db5 Use canonical path when possible
9af4df5d Made exodus sessionIO saved url records consistent
6b6a2ec8 Make displayed url shown as absolute path after loading smtk model
55ac73f2 Made loading and writing mesh collections also handle relative path.
6f62805d

 Added FileLocation class for handling relative path
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !46

When we write out the mesh collections into files on disk while exporting smtk model, which will reference
these mesh files (and model files), we want the mesh and model files to be relative to the smtk file, so that all the files can be bundled together and shared with other people.

Yumin Yuan authored Feb 17, 2016 and Kitware Robot committed Feb 17, 2016

f1cf2120 Remove some debugging code
07431452 Safe guard against some meshinfo query by handle range
5a216da4 UI logic to handle mesh changes after model edge op in tree view
d3104f6d

 Made discrete edge op also doing related mesh op
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !48