-
-
Notifications
You must be signed in to change notification settings - Fork 119
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2271 from hannobraun/geometry
Store `SurfacePath` of `HalfEdge` in geometry layer
- Loading branch information
Showing
11 changed files
with
195 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
use super::SurfacePath; | ||
|
||
/// The geometry of a half-edge | ||
#[derive(Copy, Clone)] | ||
pub struct HalfEdgeGeometry { | ||
/// # The path of the half-edge | ||
/// | ||
/// ## Implementation Note | ||
/// | ||
/// Currently, all curve-related geometry is defined locally, in terms of | ||
/// the surface that the curve is on (or purely in 2D, if there is no | ||
/// surface associated with this geometry). However, curves exist globally, | ||
/// independently of surfaces. Half-edges in multiple surfaces can refer to | ||
/// the same curve, and in fact, that is the whole reason for their | ||
/// existence as a topological object. | ||
/// | ||
/// This contradiction, globally defined curves but locally defined curve | ||
/// geometry, is the reason that this curve geometry is defined right here, | ||
/// associated with a locally existing half-edge. (And, I might add, | ||
/// redundantly so, as multiple half-edges within the same surface context | ||
/// can refer to the same curve.) | ||
/// | ||
/// Instead, it should be possible to define curve geometry *either* locally | ||
/// or globally. Then that respective definition can be associated with the | ||
/// curve (and possibly, in addition, a surface). How exactly that is going | ||
/// to work is up in the air. | ||
/// | ||
/// The point of all this exposition is to clarify that this field doesn't | ||
/// really belong here. It exists here for practical reasons that are, | ||
/// hopefully, temporary. | ||
pub path: SurfacePath, | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.