KA ProcessingJS Max Infinite Loop Count is Too Short
Right now it is extremely difficult to get even relatively basic simulations to run in Khan Academy's ProcessingJS editor without going over the __env__.KAInfiniteLoopCount limit, causing the project to freeze and display an error message saying that a loop is taking too long to run.
Early into the development of my current project, I ran into this problem, and I had to solve it with a really annoying workaround: I made it so that if you click on the screen, it tells the draw function to stop looping, then immediately start looping again.
The way I propose this problem be fixed is by adding the ability to modify the limit variable, at least up to maybe 5000 iterations, aka 5 times the current limit. Maybe even make an option to ignore some errors, such as '==' not being allowed at all.
Thanks for your consideration!
Another thing I'd like to briefly mention is the fact that when you splice an object out of a list, it stays in existence somewhere, causing the project to slowly grind to a halt. My best guess is that it stays in the RAM, and the computer has to read past it to get to objects that are actually still in the list.
Please sign in to leave a comment.