I created a "game of life" example.
So, if you don't know what that is, here is a link:
But, to keep things short: just create a shape by clicking on the screen and after that press the START button to get it on
(only shapes with exactly 3 neighbors stay alive in the next generation. So, a single cell just dies by clicking START )
The problem in my example is, that when I create a too big "data-grid" (in this example 80x60 cells) it slows down to 1 FPS.
Could it be that my code just sucks?! Why is the "state update" of the active object's sooooo slooooooow.
Too much objects? Fast loops maybe not that fast?! :P
Maybe I should try to realize this example with the surface object?!
Any ideas or suggestions?
if you decrease the global values "xCells" and "yCells" the program runs much faster.
But I guess it should also be possible to handle about 4500 objects without any problems.
(I mean, in other programming languages this is really not a big deal :P )