Ayaan005-dev

Thanks @davepagurek and @GregStanton — this discussion has been incredibly helpful, and I feel like I now have full clarity on both the technical concerns and the API direction. After...

@GregStanton Thanks for the update! Totally understand that it's pending approval — I’ll hold off on implementation until it’s greenlit. In the meantime, I’ll keep an eye on related PRs...

hey !@davepagurek This proposal sounds really promising in terms of reducing the cognitive load for users working with shader hooks. Automatically inferring whether a variable should be a varying or...

Hey @GregStanton , I’ve been following the discussion around `createVector()` with no arguments, and I understand the current plan is to have it return `[0, 0, 0]` with a warning....

@GregStanton Thanks for the clarification! That makes perfect sense — I hadn’t considered how the default createVector() behavior could block dimension-specific methods like cross() and scalarCross(). I’ll continue holding off...

I tested the behavior of angleMode() with both the main canvas and p5.Graphics in p5.js v2.0.5. Here are the three test cases I tried: **Case 1:** Canvas angleMode = DEGREES...

Thanks @davepagurek You were right — in my earlier test I was still calling the global sin() and cos(), which always use the main canvas’s angle mode. I updated the...

I want to make sure I fully understand the pixelDensity behavior in v1 and v2 before giving input on angleMode. From what I know: • In p5.js 1.x → pixelDensity()...

Hey everyone this is the summary of current understanding — Broadcasting & createVector() (as I understand it) Broadcasting Policy (Option 2): - Scalars (e.g. 2) and 1D vectors like [2]...

Thanks so much @limzykenneth and @sidwellr for the thoughtful clarifications — really appreciate it! I’ve updated the summary based on your feedback. If I’ve still misunderstood anything or missed a...