-
Notifications
You must be signed in to change notification settings - Fork 511
Add point on line segment constraint #422
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
Comments
This will be able with ranged constraints merged. PointOnLine has param and it can be constrained to be 0..1. |
Can this be applied to point-on-spline then? |
@phkahler I think the problem is the discontiguity between two parts of a spline. |
There is no problem to make pt-on-spline if spline is split on cubic bezier segments, but in case of SolveSpace where we have one primitive for several splines (up to 15 pts) we should invent some special derivative-function made of segments. My suggestion is to remove the current spline entity and substitute it with
So, we can support old files in the way where we substitute one big spline with small ones and applying special (G2/C2 derivatives smooth) tangency after loading. Look at NoteCAD where we have pt-to-spline and even pt-to-arbitrary function, but still have no tangent of second derivative (temporary) |
I was only thinking of the cubic spline with 4 points. I had forgotten that those are created with the same tool as the many-point splines and may be considered "the same thing" when they're actually sort-of different. I know the more complex version is actually composed of many instances of the simple version internally, but it still begs the question of how to transition a constrained point from one segment to the next. It wouldn't seem right to allow it for one curve and not another when they are created with the same tool. I'd recommend doing point-on-line-segment first. Then the code will be in place to limit the range of parameters (Revolve angle may want that too). |
@phkahler it is already implemented and needs some UI/cosmetic fixes Evil-Spirit@7cb2b8f |
3.2 milestone? Is this behaviour toggleable? |
Maybe 4.0 together with #77 . |
Workaround: A chord is always <= the diameter. |
Hello, any news on this? |
Went there are "news" they will probably come from #77. Probably by merging and improving some form of Evil-Spirit@7cb2b8f |
When i set constraint for point to stay on line, it can move past the two points defining the line like this:
I think it would be usefull to have constraint that can limit point movement only between these two points, eg.:
Can you please add this?
The text was updated successfully, but these errors were encountered: