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

Constraining the entire end should be equivalent to constraining both endX and endY #5338

Open
adamchalmers opened this issue Feb 11, 2025 · 0 comments

Comments

@adamchalmers
Copy link
Collaborator

adamchalmers commented Feb 11, 2025

Currently the frontend checks if a path segment is constrained by checking that:

  • The end point is an array of length 2
  • Both X and Y components of that array are constrained

e.g. line(endAbsolute = [myX(), myY()] is fully constrained.

But this fails to recognize some kinds of fully-constrained lines. For example it wouldn't recognize that line(endAbsolute = myXY()) is fully constrained. Even though it's basically equivalent -- it's assigning the endpoint to a function's output.

This unblocks #5096

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

No branches or pull requests

1 participant