I've had several users report problems with the p5.js web editor! ⚠️
But note that p5play is not affiliated with the Processing Foundation. Unfortunately, it seems they are unwilling or unable to fix critical issues, some of which are several years old.
-
When console.log is used to print a number on
every frame, it causes big drops in frame rate.
This makes the p5.js web editor unusable
for play testing.
-
console.log doesn't print out the correct
values of arrays before and after they're
changed.
-
The sequence mode of loadAnimation doesn't
work unless you use backticks for the name
of the image file.
I've had several users report problems with the p5.js web editor!⚠️
But note that p5play is not affiliated with the Processing Foundation. Unfortunately, it seems they are unwilling or unable to fix critical issues, some of which are several years old.
When console.log is used to print a number on
every frame, it causes big drops in frame rate.
This makes the p5.js web editor unusable
for play testing.
console.log doesn't print out the correct
values of arrays before and after they're
changed.
The sequence mode of loadAnimation doesn't
work unless you use backticks for the name
of the image file.