Official iT2D Documentation Feedback
by Michael Perry · in iTorque 2D · 09/27/2008 (11:01 am) · 102 replies
======================================================================
This Thread Is The Official Documentation Feedback Area For ALL Versions of iTorque 2D
If you want to quick search for all iTGB Doc Updates, perform a keyword search in your browser for
"Documentation Update:"
======================================================================
Hey everyone. It's about time we have a central thread for iT2D users to post their feedback in regard to documentation.
We have similar threads going on in the other forums forum, and so far the feedback has been overwhelmingly positive, constructive, and very helpful to the doc writers...so let's keep that going with iT2D=)
Purpose of the Thread:
- Provide a central thread for iT2D users to post their thoughts, suggestions, and criticisms about documentation.
Targets:
- Official documentation provided by TorquePowered, TDN articles, and user submitted docs/tutorials.
Suggestions for Posts:
- What is the #1 thing you would like added to the official docs?
- What area of the docs do you think needs the most work?
- What do you see in other tech docs, be it for other Torque engines or non-Torque tech, that you think would be beneficial to have in the docs?
- What are your feeling on TDN vs how the current official docs are presented?
- Bring attention to resources, tutorials, articles, or community member submissions you think should be merged into the official docs
...etc, etc
So, the overall concept of this thread is pretty simple. This is your chance to talk until your face turns blue about what you want from the docs.
Be as clear, descriptive, and specific as you can!
This Thread Is The Official Documentation Feedback Area For ALL Versions of iTorque 2D
If you want to quick search for all iTGB Doc Updates, perform a keyword search in your browser for
"Documentation Update:"
======================================================================
Hey everyone. It's about time we have a central thread for iT2D users to post their feedback in regard to documentation.
We have similar threads going on in the other forums forum, and so far the feedback has been overwhelmingly positive, constructive, and very helpful to the doc writers...so let's keep that going with iT2D=)
Purpose of the Thread:
- Provide a central thread for iT2D users to post their thoughts, suggestions, and criticisms about documentation.
Targets:
- Official documentation provided by TorquePowered, TDN articles, and user submitted docs/tutorials.
Suggestions for Posts:
- What is the #1 thing you would like added to the official docs?
- What area of the docs do you think needs the most work?
- What do you see in other tech docs, be it for other Torque engines or non-Torque tech, that you think would be beneficial to have in the docs?
- What are your feeling on TDN vs how the current official docs are presented?
- Bring attention to resources, tutorials, articles, or community member submissions you think should be merged into the official docs
...etc, etc
So, the overall concept of this thread is pretty simple. This is your chance to talk until your face turns blue about what you want from the docs.
Be as clear, descriptive, and specific as you can!
About the author
Programmer.
#102
// This function is called when this behavior is added
// to an object (aka owner)
function MovementBehavior::onBehaviorAdd(%this)
{
// If we do not have our stock ActionMap, do nothing
if (!isObject(moveMap))
{
// Print this error to the console
echo("***ERROR: ActionMap moveMap does not exist!***");
return;
}
// Bind our keys to the keyboard
// bindObj(device, action, command, object)
moveMap.bindObj(getWord(%this.upKey, 0), getWord(%this.upKey, 1), "moveUp", %this);
moveMap.bindObj(getWord(%this.downKey, 0), getWord(%this.downKey, 1), "moveDown", %this);
moveMap.bindObj(getWord(%this.leftKey, 0), getWord(%this.leftKey, 1), "moveLeft", %this);
moveMap.bindObj(getWord(%this.rightKey, 0), getWord(%this.rightKey, 1), "moveRight", %this);
// up, down, left and right are dynamic variables
// They are created for the first time here, with default values set to 0
// These are essentially on/off flags used by the updateMovement function
%this.up = 0;
%this.down = 0;
%this.left = 0;
%this.right = 0;
}
It's at iTorque2D documentation/Tutorials/Rainy Day/Keyboard behavior Script chapter.
04/25/2012 (9:21 am)
Please add moveMap.push(); line at the end of the following function:// This function is called when this behavior is added
// to an object (aka owner)
function MovementBehavior::onBehaviorAdd(%this)
{
// If we do not have our stock ActionMap, do nothing
if (!isObject(moveMap))
{
// Print this error to the console
echo("***ERROR: ActionMap moveMap does not exist!***");
return;
}
// Bind our keys to the keyboard
// bindObj(device, action, command, object)
moveMap.bindObj(getWord(%this.upKey, 0), getWord(%this.upKey, 1), "moveUp", %this);
moveMap.bindObj(getWord(%this.downKey, 0), getWord(%this.downKey, 1), "moveDown", %this);
moveMap.bindObj(getWord(%this.leftKey, 0), getWord(%this.leftKey, 1), "moveLeft", %this);
moveMap.bindObj(getWord(%this.rightKey, 0), getWord(%this.rightKey, 1), "moveRight", %this);
// up, down, left and right are dynamic variables
// They are created for the first time here, with default values set to 0
// These are essentially on/off flags used by the updateMovement function
%this.up = 0;
%this.down = 0;
%this.left = 0;
%this.right = 0;
}
It's at iTorque2D documentation/Tutorials/Rainy Day/Keyboard behavior Script chapter.
Associate Geoff Beckstrom
Thank you for your feedback. I don't have perfect answers for you right now but I want to reply to give everyone an update on GarageGames documentation.
The GarageGames doc team has been 100% involved in finishing the Torque 3D 1.2 release and its accompanying official docs, user guides, and tutorials.
Once that release is out the door - I will be creating a master list of documentation and tutorial upgrades to work on in the future.
Your mention of "Use Physics On" is a definite must addition to the iT2D documentation and I have taken note of it.
It is my desire to increase the number of both text and video based tutorials on all of the Torque engines. But to do it at the right standards - which takes time and resources.
As I begin to prioritize my list of documentation improvements and tutorial additions - community requests will be one of the most important factors.
In the meantime the Official iT2D docs are your best first line of reference and then specific questions here in the community forums is the next best place to get answers and help on your projects.