Synchronize access to array

[GoToLoop]

@pcremades

I’m not sure if serialEvent() runs in a different Thread, but it seems to be like that.

Most Processing libs that have callback names w/ the word “event” on them are indeed threaded.

@pcremades

I don’t even know if that would be the right way to solve the problem.

There are many ways to workaround threading access/mutation; but I prefer to start w/ the simplest 1s before attempting more advanced techniques.

If your sketch just needs to refresh the draw() when a new data arrives, you can simply use this noLoop()/redraw() combo:

Map function worked in Processing 2 and early 3.. But broke in 3.5.3. Need guidance

Mutating the sketch’s main canvas outside the “Animation Thread” crashes the program! Callback serialEvent() is run by the Serial’s Thread btW. So even calling something like background() can be fatal! Actually, due to a bad design, any Processing function which depends on color() will get wrong results when they’re multithreading invoked! So any canvas mutating operations should be moved to draw() or called by it. Here’s a post link for…