bezierCurveTo incorrect path when performing stroke

Expected Behaviour

Draw an oval 1.

Actual Behaviour

draws a “flower” 1.

Steps To Reproduce

points = [
  246, 338, 246, 382,
  246, 414, 300, 414,
  366, 414, 366, 371,
  366, 338, 327, 338
];
ctx.strokeColor = '#000';
ctx.beginPath();
     ctx.moveTo(points[i].p[14], points[i].p[15]); //each bezierCurve strangely centers back to the start point moveTo! 
    ctx.bezierCurveTo(points[i].p[14], points[i].p[15],points[i].p[0], points[i].p[1], points[i].p[2], points[i].p[3]);
    ctx.bezierCurveTo(points[i].p[2], points[i].p[3],points[i].p[4], points[i].p[5], points[i].p[6], points[i].p[7]);
    ctx.bezierCurveTo(points[i].p[6], points[i].p[7],points[i].p[8], points[i].p[9], points[i].p[10], points[i].p[11]);
    ctx.bezierCurveTo(points[i].p[10], points[i].p[11],points[i].p[12], points[i].p[13], points[i].p[14], points[i].p[15]);
    ctx.stroke();
    // if one uses ctx.fill() instead this will be an oval though

Platform

OS: windows 11 Node Version: 17.0.1 NPM Version: latest PureImage Version: latest

Any Additional Info

similar behavior for ctx.quadraticCurveTo but this mostly not strokes at all.

[joshmarinacci]

I think I figured it out. The flatten_path is supposed to update the ‘curr’ variable in every segment of the path, but it wasn’t doing so for the Bezier curves. Can you test if the change above fixes it for you? Up can just add the one line above in the diff.

[joshmarinacci]

Oops. I forgot to npm build before publishing. Fixed. Look for 0.3.8