Increasing access
Would make this functionality available to those with lower techical ability or understanding
Most appropriate sub-area of p5.js?
- Accessibility
- Color
- Core/Environment/Rendering
- Data
- DOM
- Events
- Image
- IO
- Math
- Typography
- Utilities
- WebGL
- Build process
- Unit testing
- Internationalization
- Friendly errors
- Other (specify if possible)
Feature enhancement details
Sub-area: p5.storageBuffer, WebGPU, p5.strands
Currently, p5.storageBuffer supports .read(), .set(), and .update() methods, but no method for deleting or destroying the buffer. It would be useful to add a .delete() method or deleteStorage(buffer).
This is seemingly currently achievable with p5.storageBuffer.buffer.destroy(), as pointed out by @davepagurek , though I didn't test it deeply
Reactions are currently unavailable
Increasing access
Would make this functionality available to those with lower techical ability or understanding
Most appropriate sub-area of p5.js?
Feature enhancement details
Sub-area: p5.storageBuffer, WebGPU, p5.strands
Currently, p5.storageBuffer supports .read(), .set(), and .update() methods, but no method for deleting or destroying the buffer. It would be useful to add a .delete() method or deleteStorage(buffer).
This is seemingly currently achievable with p5.storageBuffer.buffer.destroy(), as pointed out by @davepagurek , though I didn't test it deeply