[QUOTE=Ashley] Why not just select the object you want to create instead of the family?
Edit: if you're trying to create an object by its name, use a series of subevents, e.g.
if name = "obj1", create sprite1
if name = "obj2", create sprite 2
I'm sorry, but this isn't the solution that I'm looking for, my intention is optimize the gamecode. Imagine if in the family there's 100 sprites, would have to add 100 events just like the one you mentioned.
You say: Why not just select the object you want to create instead of the family?
Then I say: Why not with families?
As Yann mentioned, for game level editors and many other things, this will be very helpful if it's possible.
In construct 1 I can do what Yann mentioned. Can't Construct 2 be able to do that too?
I've also made many suggestions on another topic that the only purpose is to make the Construct2 tool more powerful in the issue of expanding the possibilities of game creation.
Please understand that I'm just giving new ideas for C2 that are already possible to do in Construct1.
If these things will in the future be implemented in C2 then it's okay, I know that take time and also there's priorities sometimes.
ps:sorry for my english ;)