Adobe Director Basics

ADOBE DIRECTOR BASICS
3D: Controlling appearance
v3DMember= member("3D")
pChassis = v3DMember.newGroup("Chassis")
vName = "Wheel_"
vResource = v3DMember.newModelResource(vName, #cylinder)
vResource.height = 10
vRadius = vResource.topRadius
repeat with ii = 1 to 4
vModel = v3DMember.newModel(vName&ii, vResource)
vModel.rotate(0, 0, 90)
vX = (ii mod 2) * 50 - 25
vZ = (ii > 2) * 70 - 35
vModel.translate(vX, vRadius, vZ, #world)
pChassis.addChild(vModel, #preserveWorld)
end repeat
pChassis.scale(0.20)
pChassis.rotate(0, 30, 0)
Node hierarchy
Each node in a 3D world may have one parent and any number of children. By default, each new model is set as a child
of the group(“World”). See “Group("World")” on page 93 for more details.
Each child node inherits the transform of its parent node as a frame of reference. The final position, rotation, and scale
of a model in the world depends on the transform of each node in its hierarchy of parents. See “Frame of reference”
on page 97 for more details.
The primary benefit of these parent-child relationships is that they make it easier to move complex models around in
the 3D world and to have the component parts of those models move together in the proper way. In the example of a
car, if the wheels of the car are defined as children of the car model, then moving the car will cause the wheels to be
moved with the car in the expected manner. If no parent-child relationship is defined between the car and the wheels,
moving only the car causes the wheels to be left behind in their original position in the world.
Scripting terms to use with parent-child relationships
You can use these scripting terms when you are working with parent-child relationships:
node.addChild()
node.child.count (Lingo) or aNode.count("child") (JavaScript)
node.child() (Lingo) or node.getPropRef("child", aIndex) (JavaScript)
node.parent
To test these terms, download and launch the movie WheelDemo.dir.
Last updated 8/26/2011
91