Timeline for Separate update and render
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2012 at 19:23 | vote | accept | IluTov | ||
| Nov 23, 2012 at 18:48 | comment | added | House | @NSAddict If this removes all the advantages of multi-threading then you're not threading the right parts of your code. Eric has given you a correct answer that solves your concurrent modification issues. Deciding what code to thread is a different problem. | |
| Nov 23, 2012 at 18:14 | comment | added | Eric B | Updating and Rendering have to happen in sequence, there are no advantages to multithreading them at all. This is just a way to sequence them if you have threads in place already. | |
| Nov 23, 2012 at 17:34 | comment | added | IluTov | Just wanted to ask this, I loose the advantages of multithreading with this... | |
| Nov 23, 2012 at 16:56 | comment | added | ccxvii | How is this an improvement over just using a single thread? | |
| Nov 23, 2012 at 14:58 | history | edited | Eric B | CC BY-SA 3.0 | deleted 9 characters in body |
| Nov 23, 2012 at 14:46 | history | edited | Eric B | CC BY-SA 3.0 | added 81 characters in body |
| Nov 23, 2012 at 14:38 | history | answered | Eric B | CC BY-SA 3.0 |