feat: Solve following mouse pointer #8991
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
jtran
force-pushed
the
jtran/solve-following-pointer
branch
from
275a82c to
4752813
Compare
jtran
force-pushed
the
jtran/solve-following-pointer
branch
from
4752813 to
b9ff5bb
Compare
jtran
force-pushed
the
jtran/solve-following-pointer
branch
from
76f7399 to
178b835
Compare
jtran
force-pushed
the
jtran/solve-following-pointer
branch
from
178b835 to
44fae63
Compare
jtran
force-pushed
the
jtran/solve-following-pointer
branch
from
44fae63 to
62db938
Compare
jtran
force-pushed
the
jtran/solve-following-pointer
branch
from
62db938 to
7155c3f
Compare
jtran
force-pushed
the
jtran/solve-following-pointer
branch
from
7155c3f to
2650266
Compare
jtran
force-pushed
the
jtran/solve-following-pointer
branch
from
2650266 to
ee99a49
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the user edits segments, assume this is the mouse or other pointing device dragging segments. When executing points, either explicit ones via
point()or implicit ones vialine(), if they are in the dragged set, create an optional constraint that is that point's coordinate fixed to the initial value of the x and yvars. Then, when solving, use ezpz's newsolve_with_priority()KittyCAD/ezpz#147 with required constraints at priority 0 and optional constraints at level 1.