Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

- Displaying labels for anchor numbers #79

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

salvicode
Copy link

Description

Sometimes I get lost among the anchor points so I decided to add this feature for having possibility to see the order of anchor points.

Screen Shot 2020-11-01 at 19 51 48

  • Implemented toggle setting
  • Added size/color settings

* Implemented toggle setting
* Added size/color settings
@NeatWolf
Copy link

NeatWolf commented Nov 4, 2020

I know it's a bit out of topic, yet, this made me remember: is there an easy way to reverse the point order (keeping the shape) of a path while keeping the shape (manually tweaked handles may not be trivial to flip in 3 dimensions?)

@salvicode
Copy link
Author

I know it's a bit out of topic, yet, this made me remember: is there an easy way to reverse the point order (keeping the shape) of a path while keeping the shape (manually tweaked handles may not be trivial to flip in 3 dimensions?)

Isn't it just a reversing array of the points in BezierPath. But I might be mistaken and there are some other special cases. But all the points(anchor and control) are stored in this points field. Probably using some linq Reverse will do the trick. But I have not studied the matter deeply. Maybe the author @SebLague is the person we need to address here.

@AdamBebko
Copy link

This would be really helpful as well as the reversing.

JerryVerhoeven added a commit to JerryVerhoeven/Path-Creator that referenced this pull request Sep 19, 2023
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.

4 participants