Skip to content

Trace endings jagged when the trace does not cross its start #117

Description

@dustenhubbard

Problem

A trace whose end does not cross its start renders with a jagged ending instead of closing cleanly. Legacy handled this by simplifying on close, so the result was smooth (reported by KH).

Proposed

Simplify or snap the endpoint on close so a trace that nearly meets its start closes cleanly, matching Legacy behavior. This is core tracing quality, not a display tweak.

Part of #66.


Source: PyReconstruct Wishlist, Tracing / Tools, "Closing contours" (KH, Jul 13 2023).

If I do not CROSS the start of the trace, but instead end the trace slightly before the start point, depending on exactly where my pen is wrt to the start point, the ending can be unpredictable. ... in Legacy Reconstruct, this potential issue is solved by 'simplifying' the trace once it is closed.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions