Threads - Revision history

Matt: Reverted edits by Amesycyxa (Talk); changed back to last version by Jochen

2010-11-26T19:39:32Z

Reverted edits by Amesycyxa (Talk); changed back to last version by Jochen

Amesycyxa at 10:14, 24 November 2010

2010-11-24T10:14:36Z

Jochen at 23:22, 3 June 2008

2008-06-03T23:22:39Z

Jochen at 23:22, 3 June 2008

2008-06-03T23:22:27Z

Jochen at 23:19, 3 June 2008

2008-06-03T23:19:14Z

Jochen at 19:13, 7 February 2008

2008-02-07T19:13:23Z

Jochen at 19:12, 7 February 2008

2008-02-07T19:12:57Z

Jochen at 19:12, 7 February 2008

2008-02-07T19:12:45Z

Jochen at 19:12, 7 February 2008

2008-02-07T19:12:28Z

Jochen at 19:11, 7 February 2008

2008-02-07T19:11:45Z

@@ Line 1: / Line 1: @@
-=[http://odygobyciqi.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
+Rendering and it's threads are now part of our jmonkey plugin:[http://wiki.rifidi.org/index.php/Rifidi:jmeswt jmeswt]<br/>
-Rendering and it's threads are now part of our jmonkey plugin:[http://wiki.rifidi.org/index.php/Rifidi:jmeswt jmeswt]&lt;br/&gt;
+Documentation in this chapter is from now on obsolete!<br/>
-Documentation in this chapter is from now on obsolete!&lt;br/&gt;
+Designer runs as a combination of eclipse and a 3d engine.<br/>
-Designer runs as a combination of eclipse and a 3d engine.&lt;br/&gt;
+It is very important to closely look where things are going.<br/>
-It is very important to closely look where things are going.&lt;br/&gt;
+<br/>
-&lt;br/&gt;
+<br/>
-&lt;br/&gt;
 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. &lt;br/&gt; 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.&lt;br/&gt;
+* 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/>
-&lt;br/&gt;
+<br/>
-Old stuff:&lt;br/&gt;
+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 [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.&lt;br/&gt;THIS METHOD IS BLOCKING AND IF  CALLED WHEN UPDATETHREAD IS IN THE PAUSEDSTATE WILL BLOCK FOREVER!!&lt;br/&gt;
+* 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/>
-&lt;br/&gt;
+<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.
-&lt;br/&gt;
+<br/>

@@ 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]<br/>
+=[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!<br/>
+Rendering and it's threads are now part of our jmonkey plugin:[http://wiki.rifidi.org/index.php/Rifidi:jmeswt jmeswt]&lt;br/&gt;
-Designer runs as a combination of eclipse and a 3d engine.<br/>
+Documentation in this chapter is from now on obsolete!&lt;br/&gt;
-It is very important to closely look where things are going.<br/>
+Designer runs as a combination of eclipse and a 3d engine.&lt;br/&gt;
-<br/>
+It is very important to closely look where things are going.&lt;br/&gt;
-<br/>
+&lt;br/&gt;
 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/>
+* GameTaskQueueManager.getInstance().render()/update() can be called from every part of the application and should be used to submit things to the 3d engine. &lt;br/&gt; 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.&lt;br/&gt;
-<br/>
+&lt;br/&gt;
-Old stuff:<br/>
+Old stuff:&lt;br/&gt;
 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.<br/>THIS METHOD IS BLOCKING AND IF  CALLED WHEN UPDATETHREAD IS IN THE PAUSEDSTATE WILL BLOCK FOREVER!!<br/>
+* 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.&lt;br/&gt;THIS METHOD IS BLOCKING AND IF  CALLED WHEN UPDATETHREAD IS IN THE PAUSEDSTATE WILL BLOCK FOREVER!!&lt;br/&gt;
-<br/>
+&lt;br/&gt;
 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/>
+&lt;br/&gt;

@@ Line 3: / Line 3: @@
 Designer runs as a combination of eclipse and a 3d engine.<br/>
 It is very important to closely look where things are going.<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/>

← Older revision		Revision as of 23:22, 3 June 2008
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]<br/>
		+	Documentation in this chapter is from now on obsolete!<br/>
	Designer runs as a combination of eclipse and a 3d engine.<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/>		It is very important to closely look where things are going.<br/>

@@ Line 4: / Line 4: @@
 * 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/>
 * 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/>
 * 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/>