Don't take this the wrong way, but your code is clearly written by a novice. Duplicated effort (compileRows recomputes work done in makeSprites), two for-loops doing a single task instead of a single for-loop doing two tasks, manually enumerated for-loops (1*width, 2*width, ..., name1, name2, ...), and having your Animation class take a billion arguments seems like an awkward design.
Do you have any C++ code for comparison? Also, it's kinda unfair to make generalizations about a language based on your experience with some random game engine's interface...
30-Sep-2017 08:34:37
- Last edited on
30-Sep-2017 09:30:09
by
Icy Spring