Isaac Garzón

Thanks! I saw that branch, but I couldn't make heads or tails of the visualisations. Personally I find plotting the solver's guesses against the function graph and derivatives to be...

@phkahler all of the PNG files under `res/cocoa/AppIcon.iconset`.

Working fine with latest master (60d0dab0b62cd50f01981a4669233aca9f4f1806), both when running `cd /bin && ./solvespace ~/files/feet-10deg.slvs` as well as when running `cd ~/files && /bin/solvespace feet-10deg.slvs` (reading your description, it wasn't clear...

> This may avoid copying a few bytes here and there (as in [`SplitInHalf`](https://github.com/solvespace/solvespace/blob/a5d40f81e3c2fccf9fd1cf28de6b4d4485fde068/src/srf/raycast.cpp#L135)) but in my opinion it is not worth it. The many `curve.` and to a lesser...

@ruevs thanks for the links to past discussions and ideas! I've seen some of them, but definitely not all of them. I'll make sure to take the information in them...

I added a different approach to achieve the same result, which hopefully addresses the concerns raised (assuming such a change seems reasonable despite not having an impact on the existing...

I only used `Curve` because I didn't want to add to the confusion by having a a type named `Surface` nested inside `SSurface`, but if an abbreviation is acceptable, the...

> In my opinion this is mostly syntactic sugar - makes the code longer and less readable. My motivation for doing it is mainly to avoid the [copy needed during...

> Draw two line segments that share a point, and then constrain the shared point as "where dragged". Obviously all 3 points can be dragged, But one of the line...

> A better option is to actually share the same point between entities, but then we'd need reference counting on point entities. That would be a major refactoring and brake...