Recent changes to Setup

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 24 May 2012 19:44:42 -0000

--- v8
+++ v9
@@ -18,12 +18,12 @@
 
  
 
-You could even make several engines if you wanted to keep categories of tweens separate.
+Where myTweenEngine can be any unique name you prefer.  You could even make several engines if you wanted to keep categories of tweens separate.
 
 Frame Updates
 ======
 
-It's not possible to get Torque to call an *onUpdate()* on **Twillex** objects each frame.  The scene graph will have to be kind and call *Twillex::onUpdate()*.  For example:
+In *Torque2D*, it's not possible to get Torque to call an *onUpdate()* on **Twillex** objects each frame.  (That only works for scene objects and **Twillex** is not one.)  The scene graph will have to be kind and call *Twillex::onUpdate()*.  For example:
 
 
 function mySceneGraph::onUpdateSceneTick(%this) {

@@ -34,6 +34,17 @@
  
 
 Note that you don't have to call *onUpdate()* on the individual *Tweens*, just the **Twillex** engines.
+
+In *Torque3D*, there is no *scene graph* update method.  Instead call
+
+
+       myTweenEngine.startUpdates();

+
+     
+
+This will cause updates every 1/30th of a second.  If you prefer slower updates, you can pass in a parameter that specifies milliseconds between updates, such as 60 or 120.
+
+Note that **Torque2D** users can also use **startUpdates()** but this author prefers the first method.
 
 Use
 ======

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 02 Feb 2012 20:28:27 -0000

--- v7 
+++ v8 
@@ -5,44 +5,46 @@
 
 Setup and tear-down work as usual in Torque.  First, include the *Twillex.cs* script.  (**Twillex** is written as a single script file.)
 
-~~~~~~
-//
-exec("/Twillex.cs");
-~~~~~~
-
+
+exec("<your_path>/Twillex.cs");
+
+ 
+
 Then, create a **Twillex** *engine* to run your tweens.  For instance
 
-~~~~~~
-//
+
+
 Twillex::create(myTweenEngine);
-~~~~~~
+
+ 
 
 You could even make several engines if you wanted to keep categories of tweens separate.
 
 Frame Updates
 ======
 
 It's not possible to get Torque to call an *onUpdate()* on **Twillex** objects each frame.  The scene graph will have to be kind and call *Twillex::onUpdate()*.  For example:
 
-~~~~~~
-//
-function mySceneGraph::onUpdateSceneTick(%this) {
-   // do all the other stuff also
-   myTweenEngine.onUpdate();
+
+function mySceneGraph::onUpdateSceneTick(%this) {

+       // do all the other stuff also

+       myTweenEngine.onUpdate();

 }
-~~~~~~
+
+ 
 
 Note that you don't have to call *onUpdate()* on the individual *Tweens*, just the **Twillex** engines.
 
 Use
 ======
 [Example Use](Example Use) is a page with several examples of creating and using *Tweens*.
 
 Teardown
 ======
 
-In the end, delete your Twillex objects as usual:
-
-~~~~~~
+In the end, delete your **Twillex** objects as usual:
+
+
 myTweenEngine.delete();
-~~~~~~
+
+

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 02 Feb 2012 20:17:57 -0000

--- v6 
+++ v7 
@@ -1,40 +1,42 @@
-To create a **Twillex** engine and **Tweens** requires set up, tear down, and frame updates.
-
+To create a **Twillex** engine and *Tweens* requires set up, tear down, and frame updates.
+
 Setup
 ------
 
 Setup and tear-down work as usual in Torque.  First, include the *Twillex.cs* script.  (**Twillex** is written as a single script file.)
 
 ~~~~~~
 //
 exec("/Twillex.cs");
 ~~~~~~
 
-
 Then, create a **Twillex** *engine* to run your tweens.  For instance
 
 ~~~~~~
 //
 Twillex::create(myTweenEngine);
 ~~~~~~
 
 You could even make several engines if you wanted to keep categories of tweens separate.
 
 Frame Updates
 ======
 
 It's not possible to get Torque to call an *onUpdate()* on **Twillex** objects each frame.  The scene graph will have to be kind and call *Twillex::onUpdate()*.  For example:
 
 ~~~~~~
 //
 function mySceneGraph::onUpdateSceneTick(%this) {
    // do all the other stuff also
    myTweenEngine.onUpdate();
 }
 ~~~~~~
 
-Note that you don't have to call *onUpdate()* on the individual **Tweens**, just the **Twillex** engines.
-
+Note that you don't have to call *onUpdate()* on the individual *Tweens*, just the **Twillex** engines.
+
+Use
+======
+[Example Use](Example Use) is a page with several examples of creating and using *Tweens*.
 
 Teardown
 ======

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 02 Feb 2012 20:10:46 -0000

--- v5 
+++ v6 
@@ -20,23 +20,27 @@
 
 You could even make several engines if you wanted to keep categories of tweens separate.
 
-Teardown
-======
-
-In the end, delete your Twillex objects as usual:
-
-~~~~~~
-myTweenEngine.delete();
-~~~~~~
-
+Frame Updates
+======
+
 It's not possible to get Torque to call an *onUpdate()* on **Twillex** objects each frame.  The scene graph will have to be kind and call *Twillex::onUpdate()*.  For example:
 
 ~~~~~~
 //
 function mySceneGraph::onUpdateSceneTick(%this) {
    // do all the other stuff also
    myTweenEngine.onUpdate();
 }
 ~~~~~~
 
 Note that you don't have to call *onUpdate()* on the individual **Tweens**, just the **Twillex** engines.
+
+
+Teardown
+======
+
+In the end, delete your Twillex objects as usual:
+
+~~~~~~
+myTweenEngine.delete();
+~~~~~~

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 02 Feb 2012 20:10:02 -0000

--- v4 
+++ v5 
@@ -14,6 +14,7 @@
 Then, create a **Twillex** *engine* to run your tweens.  For instance
 
 ~~~~~~
+//
 Twillex::create(myTweenEngine);
 ~~~~~~

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 02 Feb 2012 20:09:30 -0000

--- v3 
+++ v4 
@@ -6,32 +6,32 @@
 Setup and tear-down work as usual in Torque.  First, include the *Twillex.cs* script.  (**Twillex** is written as a single script file.)
 
 ~~~~~~
-
+//
 exec("/Twillex.cs");
 ~~~~~~
 
 
 Then, create a **Twillex** *engine* to run your tweens.  For instance
 
 ~~~~~~
 Twillex::create(myTweenEngine);
 ~~~~~~
 
 You could even make several engines if you wanted to keep categories of tweens separate.
 
 Teardown
 ======
 
 In the end, delete your Twillex objects as usual:
 
 ~~~~~~
 myTweenEngine.delete();
 ~~~~~~
 
 It's not possible to get Torque to call an *onUpdate()* on **Twillex** objects each frame.  The scene graph will have to be kind and call *Twillex::onUpdate()*.  For example:
 
 ~~~~~~
-
+//
 function mySceneGraph::onUpdateSceneTick(%this) {
    // do all the other stuff also
    myTweenEngine.onUpdate();

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 02 Feb 2012 20:09:19 -0000

--- v2 
+++ v3 
@@ -6,30 +6,32 @@
 Setup and tear-down work as usual in Torque.  First, include the *Twillex.cs* script.  (**Twillex** is written as a single script file.)
 
 ~~~~~~
+
 exec("/Twillex.cs");
 ~~~~~~
 
 
 Then, create a **Twillex** *engine* to run your tweens.  For instance
 
 ~~~~~~
 Twillex::create(myTweenEngine);
 ~~~~~~
 
 You could even make several engines if you wanted to keep categories of tweens separate.
 
 Teardown
 ======
 
 In the end, delete your Twillex objects as usual:
 
 ~~~~~~
 myTweenEngine.delete();
 ~~~~~~
 
 It's not possible to get Torque to call an *onUpdate()* on **Twillex** objects each frame.  The scene graph will have to be kind and call *Twillex::onUpdate()*.  For example:
 
 ~~~~~~
+
 function mySceneGraph::onUpdateSceneTick(%this) {
    // do all the other stuff also
    myTweenEngine.onUpdate();

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 02 Feb 2012 20:08:43 -0000

--- v1 
+++ v2 
@@ -1,43 +1,39 @@
-## Setup/Teardown/Maintenance
-
-To create a Twillex engine requires set up, tear down, and frame updates.
-
-Setup and tear-down work as usual in Torque.
-
-First, include the script
-
-~~~~~~
+To create a **Twillex** engine and **Tweens** requires set up, tear down, and frame updates.
+
+Setup
+------
+
+Setup and tear-down work as usual in Torque.  First, include the *Twillex.cs* script.  (**Twillex** is written as a single script file.)
+
+~~~~~~
 exec("/Twillex.cs");
 ~~~~~~
 
 
-Then, create a Twillex engine to run your tweens.
-
-~~~~~~
-//
+Then, create a **Twillex** *engine* to run your tweens.  For instance
+
+~~~~~~
 Twillex::create(myTweenEngine);
 ~~~~~~
 
-
-You could even make several Twillex engines if you wanted to keep categories of Tweens separate.  In the end, delete your Twillex objects as usual:
+You could even make several engines if you wanted to keep categories of tweens separate.
+
+Teardown
+======
+
+In the end, delete your Twillex objects as usual:
 
 ~~~~~~
 myTweenEngine.delete();
 ~~~~~~
 
-
-It's not possible to get Torque to call an *onUpdate()* on Twillex objects each frame.  The scene graph will have to be kind and call Twillex::onUpdate().
-For example:
-
-
-~~~~~~
- //
- function mySceneGraph::onUpdateSceneTick(%this) {
-    // do all the other stuff also
-    myTweenEngine.onUpdate();
+It's not possible to get Torque to call an *onUpdate()* on **Twillex** objects each frame.  The scene graph will have to be kind and call *Twillex::onUpdate()*.  For example:
+
+~~~~~~
+function mySceneGraph::onUpdateSceneTick(%this) {
+   // do all the other stuff also
+   myTweenEngine.onUpdate();
 }
 ~~~~~~
 
-
-Note that you don't have to call onUpdate on the individual Tweens, just the Twillex engines.
-
+Note that you don't have to call *onUpdate()* on the individual **Tweens**, just the **Twillex** engines.

WikiPage Setup modified by Charles Patterson

Charles Patterson — Thu, 02 Feb 2012 20:03:09 -0000

## Setup/Teardown/Maintenance To create a Twillex engine requires set up, tear down, and frame updates. Setup and tear-down work as usual in Torque. First, include the script ~~~~~~ exec("/Twillex.cs"); ~~~~~~ Then, create a Twillex engine to run your tweens. ~~~~~~ // Twillex::create(myTweenEngine); ~~~~~~ You could even make several Twillex engines if you wanted to keep categories of Tweens separate. In the end, delete your Twillex objects as usual: ~~~~~~ myTweenEngine.delete(); ~~~~~~ It's not possible to get Torque to call an *onUpdate()* on Twillex objects each frame. The scene graph will have to be kind and call Twillex::onUpdate(). For example: ~~~~~~ // function mySceneGraph::onUpdateSceneTick(%this) { // do all the other stuff also myTweenEngine.onUpdate(); } ~~~~~~ Note that you don't have to call onUpdate on the individual Tweens, just the Twillex engines.