>
> ... and how does object.position = new Number3D(x,y,z) differ from
>
object.moveTo(x,y,z)? The two look really similar in the source code
>
other than an extra check in the moveTo method?
position uses a number3d to set the translation of the 3d object. moveTo
uses three number agruments. The difference is preferred way of working -
sometimes you will want to set position with number3d, other times you don't
want to have to create a number3d object just to set the position.
Ideally position should be read-only, as setting a number3d for the position
before adjusting xyz values will not update position. But this was tried and
broke backwars compatibility, therefore both are now present.
Rob
On Thu, Nov 20, 2008 at 2:47 PM, Fabrice <[EMAIL PROTECTED]> wrote:
>
> all 3 display same thing on screen, thats where it looks confusing.
> the pivot is there for instance to allow a rotation from a given point.
> same could be done with applyPosition
> In case of an export to obj format for instance, it would reveal a totally
> fucked up model in many apps
> if the vertexes would not be offsetted. Or for instance, if you want to
> make some geometry and recenter it.
> like line 385 in PathExtrude
>
> if(_recenter) {
> applyPosition( (this.minX+this.maxX)*.5, (this.minY+this.maxY)*.5,
> (this.minZ+this.maxZ)*.5);
>
> the moveTo, is there to avoid certain cases where you would need to
> generate an extra Number3D
> and acts indeed as method like the property position.
>
> Fabrice
>
>
>
>
> On Nov 20, 2008, at 3:22 PM, Jensa wrote:
>
>
>> Ah. ok. And how does this differ from object.position then?
>>
>> J
>>
>
>
--
Rob Bateman
Flash Development & Consultancy
[EMAIL PROTECTED]
www.infiniteturtles.co.uk
www.away3d.com
