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

Request option for comments to be constrained/tied to other objects #443

Closed
philtipping opened this issue Jun 22, 2019 · 3 comments · Fixed by #1035
Closed

Request option for comments to be constrained/tied to other objects #443

philtipping opened this issue Jun 22, 2019 · 3 comments · Fixed by #1035

Comments

@philtipping
Copy link

System information

SolveSpace version: 3.0~cb0fdb1c
Operating system: lubuntu 18.04

Request option for comments to be constrained/tied to other objects, and/or to each other.
I use lots of comments to label construction entities, but they all go out of alignment if an entity moves. If this is not easy to implement, can comments at least be dragged en masse when multiple comments are selected?

Have to add, am really impressed by solvespace - super stable and very slick & easy user interface - a breath of fresh air compared with other 'windows-heavy' programs. Kudos to the creator and all the contributors/maintainers.

@Evil-Spirit
Copy link
Collaborator

Also, comments should be selected by marquee like the other constraints.

@whitequark
Copy link
Contributor

IIRC comments not being selected is deliberate.

@phkahler phkahler linked a pull request May 12, 2021 that will close this issue
@phkahler
Copy link
Member

See PR #1035. Selecting a point prior to adding a comment constraint ties the comment to the point. It's not clear how they should attach to other entities, but everything has at least one point ;-)

Feel free to reopen this or create another issue if this isn't good enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants