Merge branch 'main' into experimental-features

Author: davepagurek

contributor_docs/contributor_guidelines.md

@@ -8,7 +8,9 @@ If you are looking to contribute outside of the p5.js repositories (writing tuto
 
 This is a relatively long and comprehensive document but we will try to signpost all steps and points as clearly as possible. Do utilize the table of contents to find sections relevant to you. Feel free to skip sections if they are not relevant to your planned contributions.
 
-**If you are a new contributor, you may want to start with the first section, “All about issues.” If you just want a step-by-step setup of the development process, you can look at the “Quick Get Started For Developers” section.**
+**If you are a new contributor**, be sure to check this entire document, as well as the [AI Usage Policy](https://github.com/processing/p5.js/blob/main/AI_USAGE_POLICY.md). We recommend new contributors work on one topic at a time: this means asking for assignment on one issue at a time, or submitting one PR at a time. This helps reduce overlapping work, and it helps us be more efficient with reviews. Please be mindful that almost all reviews are done by volunteers.
+
+Please note that consistently violating the contributor guidelines, the AI usage policy, and/or the code of conduct may result in temporary or permanent suspension of user accounts. We expect contributors to respond to feedback: even if you do not implement something someone asks, we expect you to reply to the comments.
 
 # Table of Contents
 

contributor_docs/p5.strands.md

@@ -237,7 +237,7 @@ let c_0 = b_1 + a_0;
 return c_0;
 ```
 
-When we generate GLSL from the graph, we start from the variables we need to output, the return values of the function (e.g. `c_0` in the example above.) From there, we can track dependencies through the DAG (in this case, `b_1` and `a_1`). Each dependency has their own dependencies. We make sure we output the dependencies for a node before the node itself.
+When we generate GLSL from the graph, we start from the variables we need to output, the return values of the function (e.g. `c_0` in the example above.) From there, we can track dependencies through the DAG (in this case, `b_1` and `a_0`). Each dependency has their own dependencies. We make sure we output the dependencies for a node before the node itself.
 
 ```mermaid
 flowchart TB

package-lock.json

@@ -126,11 +126,11 @@ class p5 {
     };
 
     if (typeof window !== 'undefined') {
-      window.addEventListener('focus', focusHandler);
-      window.addEventListener('blur', blurHandler);
-      p5.lifecycleHooks.remove.push(function () {
-        window.removeEventListener('focus', focusHandler);
-        window.removeEventListener('blur', blurHandler);
+      window.addEventListener('focus', focusHandler, {
+        signal: this._removeSignal
+      });
+      window.addEventListener('blur', blurHandler, {
+        signal: this._removeSignal
       });
 
       // Initialization complete, start runtime

src/core/main.js

@@ -2343,8 +2343,8 @@ function renderer3D(p5, fn) {
    * @beta
    * @webgpu
    * @webgpuOnly
-   * @param {Number|Array|Float32Array|Object[]} dataOrCount Either a number specifying the count of floats,
-   *   an array/Float32Array of floats, or an array of objects describing struct elements.
+   * @param {Number|Array|Float32Array|Uint32Array|Int32Array|Object[]} dataOrCount Either a number specifying the count of elements,
+   *   an array/TypedArray of values, or an array of objects describing struct elements.
    * @returns {p5.StorageBuffer} A storage buffer.
    */
   fn.createStorage = function (dataOrCount) {

src/core/p5.Renderer3D.js

@@ -190,10 +190,21 @@ async function loadMaterialTextures(materials, modelPath, instance) {
 // as the aggregate; each part gets its own localised verts with faces re-indexed
 // against them, plus its material's state.
 function buildMaterialParts(model, faceMaterials, materials) {
-  // only split when there are genuinely multiple materials. a single material
-  // (or none) stays as the geometry's own part and renders as before. one group
-  // per material, plus a null group for faces before any usemtl so none drop.
+  // one group per material, plus a null group for faces before any usemtl so
+  // none drop.
   const names = [...new Set(faceMaterials)];
+
+  // one material covering every face. the geometry is already its own part, so
+  // hand it the state directly: splitting would duplicate every vertex to say
+  // the same thing, and would stop parts[0] being the geometry itself. without
+  // this a single material model never receives its maps at all.
+  if (names.length === 1 && names[0] != null) {
+    Object.assign(model.partState, mtlToPartState(materials[names[0]]));
+    return;
+  }
+
+  // nothing to split on: no materials, or one material alongside faces that
+  // were declared before any usemtl and so have none.
   if (names.filter(name => name != null).length < 2) return;
 
   const hasUvs = model.uvs.length > 0;