Multithreading in Processing

[sterretje]

@Braunstein

Technically yes, since you can set custom rules that may include something like “a dead cell needs 0 living neighbors to come alive”, so just because of that, knowing the state of every cell is important. In practice, when using actual sensible rules (like the standard one), a dead cell that doesn’t have any living neighbors will definitely stay dead on the next frame as well, so only keeping track of living cells and their neighbors would actually be more efficient, yeah

Maybe I cause some confusion. Let me try to clarify

Is it acceptable that

1. You first check row 0 column 0 for alive neighbours and next update the frame.
2. Next check cell row 0 column 1 for alive neighbours and next update the frame.
3. Next check cell row 0 column 2 for alive neighbours and next update the frame.
   And so on.
   Once you have checked all cells in row 0 that way, move to row 1. Next to row 2 etc. Once you have done all rows, start at row 0 again

---

Can you post a basic example; it does not have to refresh the frame. At this moment I do not know what countLiveNeighbors and inArray do and how much time they take.