control copy vs clone

is this correct?:

when creating new objects with cloning you have a new "object" and when creating one with a control drag you create a new instance of an existing object?

thanks

danno55 yes that is the way I understand it. Any changes you make at object level will effect all the instances. However you make changes to each instance on the layout.

What I have found a real frustration is when making a clone it seems to make it with default settings. So if you create a Sprite. Make modifications to the default settings and then clone it you lose all modifications made. Perhaps I have missed something so far.

AngelEyes: are you using the very latest C2 release ?

1. Does it affect performance in any way?

2. If I change value of object that was created with ctrl+drag during runetime with SetValue will it affect all objects that were created similiar way from ctrl+drag of that particular object?

Changing settings in the events will affect all picked instances of an object. You use the events to filter down which ones are picked.

If you have an event trigger on the touch of an instance, that single instance is picked, all others are ignored, so only it's values change.

Kyatric, I am using the latest stable release, r139. As I am fairly new to C2, I figured stick with the stable releases, so I am sure it is my fault and not the program, when I mess something up.

AngelEyes: I can't remember exactly when this was introduced, but normally cloning an object type should not reset its properties/instance variables anymore.

I can confirm in r143, cloning an object keeps the values you modified at least for its behaviors.

Kyatric, thanks for the heads up. Maybe I will give r143 a bash. Can I install two versions alongside each other by choosing a different install directory, or will that give me clashes?

AngelEyes: You can, no issue there.

Just be sure to manage the shortcuts appropriately for you.

Kyatric, thanks will give that a go.

AngelEyes - Be aware however, if you modify your project in 143, it won't load in the older version anymore.

Paradox, thanks for the heads up.