Architecture Ideas

From WorkCDN

Multi-Threading Considerations

• The cut-scene objects run as separate threads in parallel to a rendering thread. This allows for simplified cut-scene coding in straight c# without having to manage states. However this has caused some problems with synchronization of when loading objects into the scene.
  • Perhaps we could have a "freeze screen" switch that prevents the rendering thread from updating the changes made to sprites and such until it has been "unfrozen"
    • Like a mutex? I've definitely seen some places in the code where I suspect a mutex could clean up some of this multithreaded conflict. --HanClinto 13:42, 9 November 2007 (EST)
  • or, maybe there could be a transaction mechanism that works like db transactions. Property modifications could be intercepted and queued and then processed atomically as one step in the order executed when the transaction commits.