Difference between revisions of "Threads"
From RifidiWiki
| Line 1: | Line 1: | ||
| − | Rendering and it's threads are now part of our jmonkey plugin:[http://wiki.rifidi.org/index.php/Rifidi:jmeswt jmeswt] | + | =[http://odygobyciqi.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]= |
| − | Documentation in this chapter is from now on obsolete! | + | Rendering and it's threads are now part of our jmonkey plugin:[http://wiki.rifidi.org/index.php/Rifidi:jmeswt jmeswt]<br/> |
| − | Designer runs as a combination of eclipse and a 3d engine. | + | Documentation in this chapter is from now on obsolete!<br/> |
| − | It is very important to closely look where things are going. | + | Designer runs as a combination of eclipse and a 3d engine.<br/> |
| − | + | It is very important to closely look where things are going.<br/> | |
| − | + | <br/> | |
| + | <br/> | ||
Just some rules: | Just some rules: | ||
| − | * GameTaskQueueManager.getInstance().render()/update() can be called from every part of the application and should be used to submit things to the 3d engine. | + | * GameTaskQueueManager.getInstance().render()/update() can be called from every part of the application and should be used to submit things to the 3d engine. <br/> It is very important to add and remove nodes inside callables that get submitted to the 3d engine as it might break the software if you don't do it this way.<br/> |
| − | + | <br/> | |
| − | Old stuff: | + | Old stuff:<br/> |
IF YOU HAVE BEEN USING THE HELPER CLASS REMOVE THAT CODE AS IT WILL CAUSE A DEADLOCK FROM DESIGNER 1.3 ON! | IF YOU HAVE BEEN USING THE HELPER CLASS REMOVE THAT CODE AS IT WILL CAUSE A DEADLOCK FROM DESIGNER 1.3 ON! | ||
| − | * Waiting on Futures: Sometimes it is important to be able to wait on a future when you have submitted a callable. The [http://www.rifidi.org/javadoc/designer/doc/org/rifidi/designer/utils/Helpers.html Helpers class] contains a static method called waitOnCallable. This method can be used to wait for a futue to return and is the only way (that I know of) to do this from inside the eclipse thread. | + | * Waiting on Futures: Sometimes it is important to be able to wait on a future when you have submitted a callable. The [http://www.rifidi.org/javadoc/designer/doc/org/rifidi/designer/utils/Helpers.html Helpers class] contains a static method called waitOnCallable. This method can be used to wait for a futue to return and is the only way (that I know of) to do this from inside the eclipse thread.<br/>THIS METHOD IS BLOCKING AND IF CALLED WHEN UPDATETHREAD IS IN THE PAUSEDSTATE WILL BLOCK FOREVER!!<br/> |
| − | + | <br/> | |
APPARENTLY THIS ISSUE GOT RESOLVED WITH ECLIPSE 3.3! | APPARENTLY THIS ISSUE GOT RESOLVED WITH ECLIPSE 3.3! | ||
* syncExec/asyncExec: Avoid syncExec. According to some newsgroup posts as of eclipse 3.2 there is a deadlock condition that might cause a hang on syncExec. Use asyncExec and a callback. | * syncExec/asyncExec: Avoid syncExec. According to some newsgroup posts as of eclipse 3.2 there is a deadlock condition that might cause a hang on syncExec. Use asyncExec and a callback. | ||
| − | + | <br/> | |
Revision as of 10:14, 24 November 2010
Rendering and it's threads are now part of our jmonkey plugin:jmeswt<br/> Documentation in this chapter is from now on obsolete!<br/> Designer runs as a combination of eclipse and a 3d engine.<br/> It is very important to closely look where things are going.<br/> <br/> <br/> Just some rules:
- GameTaskQueueManager.getInstance().render()/update() can be called from every part of the application and should be used to submit things to the 3d engine. <br/> It is very important to add and remove nodes inside callables that get submitted to the 3d engine as it might break the software if you don't do it this way.<br/>
<br/>
Old stuff:<br/> IF YOU HAVE BEEN USING THE HELPER CLASS REMOVE THAT CODE AS IT WILL CAUSE A DEADLOCK FROM DESIGNER 1.3 ON!
- Waiting on Futures: Sometimes it is important to be able to wait on a future when you have submitted a callable. The Helpers class contains a static method called waitOnCallable. This method can be used to wait for a futue to return and is the only way (that I know of) to do this from inside the eclipse thread.<br/>THIS METHOD IS BLOCKING AND IF CALLED WHEN UPDATETHREAD IS IN THE PAUSEDSTATE WILL BLOCK FOREVER!!<br/>
<br/> APPARENTLY THIS ISSUE GOT RESOLVED WITH ECLIPSE 3.3!
- syncExec/asyncExec: Avoid syncExec. According to some newsgroup posts as of eclipse 3.2 there is a deadlock condition that might cause a hang on syncExec. Use asyncExec and a callback.
<br/>
