Pomax
It's not even "a bug" at all - that's literally how they work. CR spines are not presented as a somehow different curve, they are presented as being *the same*...
Ah, I see. To be fair this primer is way more geared towards "for when you need to program these" rather than "for when you're designing with them". I'll think...
maybe, but again that phrasing suggests something that doesn't exist. There are no "right" default values, not even for design. There might be aesthetically pleasing ones, but that's not enough...
No, as a discussion on adding content to the primer for a special audience, this is certainly not a very minor matter, and discussions are not a waste of time....
hm, so that would be animation contexts? I think with how the sections are ordered at the moment it would make sense to put a path traversal/animation section near the...
yeah that's what I'm also leaning towards
good point - can you please file this on https://github.com/pomax/BezierInfo-2 instead? It's where all the bugs get tracked (this is just the gh-pages repository - there are still issues open...
or, based on circular arc approximations and then linear distance traversal along the arcs.
yeah, "area under a curve" for parametric curves is kind of hard due to the absence of a strict "above" or "below", but getting the area between the curve and...
as a lossless operation the translation by -(x,y)0 seems a step that generally makes sense (if only to homogenise with most other papers I've read that try to use canonical...