Difference between revisions of "RenderThread"
From RifidiWiki
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Image:Renderthread.png]] | + | THIS PAGE NEEDS A REWORK, THE DIAGRAMS ARE NOT UP TO DATE |
| + | [[Image:Renderthread.png]]<br/> | ||
[http://www.rifidi.org/javadoc/designer/doc/org/rifidi/designer/rcp/views/view3d/threads/RenderThread.html javadoc]<br/> | [http://www.rifidi.org/javadoc/designer/doc/org/rifidi/designer/rcp/views/view3d/threads/RenderThread.html javadoc]<br/> | ||
The RenderThread is instantiated and started after a new scene got loaded.<br/> | The RenderThread is instantiated and started after a new scene got loaded.<br/> | ||
| Line 5: | Line 6: | ||
As syncExec has a little problem with deadlocks (we got this from some newsgroup posts, we could never confirm this but as we were facing some deadlocks we eliminated all possible sources) we have to use asyncExec and a control variable in renderThread (running) to check if a RenderRunnable is currently running.<br/> | As syncExec has a little problem with deadlocks (we got this from some newsgroup posts, we could never confirm this but as we were facing some deadlocks we eliminated all possible sources) we have to use asyncExec and a control variable in renderThread (running) to check if a RenderRunnable is currently running.<br/> | ||
The RenderRunnable is responsible for acquiring the lock that is shared with the UpdateThread to prevent simultanious operations of both on the scene graph.<br/> | The RenderRunnable is responsible for acquiring the lock that is shared with the UpdateThread to prevent simultanious operations of both on the scene graph.<br/> | ||
| + | [[Image:RenderRunnable.png]] | ||
Latest revision as of 23:20, 3 June 2008
THIS PAGE NEEDS A REWORK, THE DIAGRAMS ARE NOT UP TO DATE
javadoc
The RenderThread is instantiated and started after a new scene got loaded.
The WorldService is responsible for controlling the states of this thread.
As syncExec has a little problem with deadlocks (we got this from some newsgroup posts, we could never confirm this but as we were facing some deadlocks we eliminated all possible sources) we have to use asyncExec and a control variable in renderThread (running) to check if a RenderRunnable is currently running.
The RenderRunnable is responsible for acquiring the lock that is shared with the UpdateThread to prevent simultanious operations of both on the scene graph.
