Skip to content

fix: do not skip strokes when using the eraser - #1817

Draft
Doublonmousse wants to merge 3 commits into
flxzt:mainfrom
Doublonmousse:eraser_skip
Draft

fix: do not skip strokes when using the eraser#1817
Doublonmousse wants to merge 3 commits into
flxzt:mainfrom
Doublonmousse:eraser_skip

Conversation

@Doublonmousse

Copy link
Copy Markdown
Collaborator

Fixes #1247

For now I take the convex hull of the polygon containing both current and previous eraser bounds (we probably can do one helper function for this or compute a closed form hull for this case, if speed is a concern) and use it to do intersection tests with geo (or use the previous code for the first down eraser event)

With another fix related to #730 to keep the visual appearance of splitted textured strokes (nothing on the performance side though)

By advancing the seed by the number of segment, thus keeping the same appearance when splitting parts of the stroke
…aser position

- if we have both current and previous position, construct a polygon of current and previous eraser bounds, take the convex hull
- use the convex hull for intersection tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Erasing faster skips some strokes

1 participant