Dave Pagurek

There's a related issue open for the p5 website repo here for the first part of this issue: https://github.com/processing/p5.js-website/issues/636 Probably the fix will be in that repo. For the latter,...

Thanks @yashodipmore! I'd be interested in knowing, before or as you're working on this task, what the potential ways of addressing this could be (e.g. do we need more semantic...

I'm sympathetic to putting the syntax at the top personally, I end up scrolling to the bottom most of the time. This is especially for functions like `image()` where the...

The core issue here is that `setAttributes` invalidates previous returned values from `createCanvas`. We're refactoring the rendering system in p5 2.0 to not do this any more, so we can...

This is fixed on the 2.0 branch now!

Looks like it works as expected if you access it like this: ```js function setup() { createCanvas(400, 400); console.log(_renderer._pInst._setupDone); } function draw() { console.log(_renderer._pInst._setupDone); noLoop(); } ``` So it seems...

I think I also agree with @lukeplowden and @Garima3110. Maybe the way to think about it is not in terms of fills and strokes, but in terms of *materials* and...

Ahh @perminder-17 you're right, those methods are going to clash, so we'll have to rename something. Maybe the hooks ones should be renamed to `defaultStrokeShader()` instead of just `strokeShader()`? It's...

That also works for me. I guess the stroke one is the only naming conflict because the shader used internally for images is the material shader, and we're just using...

oops good catch @lukeplowden, I guess if I can confuse the two already then maybe that's a sign they'd be too similar. > However couldn't `strokeShader()` both set the active...