Timeline for Is storing all game objects in a single list an acceptable design?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 18, 2012 at 22:55 | history | edited | Michael | CC BY-SA 3.0 |
fixed a typo
|
| Jan 18, 2012 at 19:16 | comment | added | Nic Foster | I agree with this, I generally have subsets of my list for objects that need to be updated each frame, and I've been considering doing the same for objects that render. However when those properties can change on the fly, managing all of the lists can be complex. When and object goes from being renderable to non-renderable, or updateable to non-updateable, and now you're adding or removing them from multiple lists at a time. | |
| Jan 18, 2012 at 18:28 | history | answered | Michael | CC BY-SA 3.0 |