Making objects

#1 T2DStaticSprite player = new T2DStaticSprite();

#2 No, I want all the attributes of the object "player" put into the Sprite player. So it's like a copy. I've tried

(TorqueObjectDatabase.Instance.FindObject("player") as T2DStaticSprite).CopyTo(player)

as well but that doesn't copy over components (the ones defined by tgbx) as well. I'm beginning to think there's no easy way to do this.

#3 Ah, I see. For that you use the clone function like you already are doing. To change the material all you would have to do is clone the object and just assign it a new material that you have made in code or in the editor (I'm not sure if there is a lookup for material names). As far as I know, a clone is a copy in every way shape and form.

#4 Clone and Copy are the same. You have full access to do whatever you want to your new copy.

#5 I've found its sometimes hard to find a clone, if I don't give it a name before I register it.

//new name
_newClone.Name = "NewClone";
//then register
TorqueObjectDatabase.Instance.Register (_newClone);

#6 Maybe this would be a good time to ask for default naming such as:

template_obj.Name = "JonathonRules"

cloned_obj1.Name = "JonathonRules1"

cloned_obj2.Name = "JonathonRules2"

and so on..

#7 I think all Parent objects should be "Pirate0"
and all child objects should be "LostBoy1"

but what you are talking about sounds cool too...

#8 Do you think that would work?

#9 Well all the names of objects would have to be the same so you would have to do "LostBoy1," "LostBoy2," etc. but that's probably what you meant anyway. If you are going to be creating them many times I would suggest having one function that creates and names them etc. Keep a variable that stores their "depth" so to speak and then you can name them accordingly.

example:

int _depthCounter = 0;

void CreatePlayer()
{
   T2DStaticSprite lostBoy = (T2DSceneObject)(TorqueObjectDatabase.Instance.FindObject("Pirate0") as T2DStaticSprite).Clone();
   lostBoy.Name = "LostBoy" + _depthCounter.ToString();
   _depthCounter++;
}

It's good coding habit to use methods like these that reuse code as opposed to making each player manually. This makes your code dynamic so you can add things later on.

#10 Hey Luke, that "+ ToString" method really does work!