Well, this wasn't the real thing I'm doing, it's just an example I threw together.

lucid: You have it backwards.

BROO: The first is too specific, and while the second would work, I was wondering if there was a way to do it without looping through every object each time. I guess there isn't right now, though.

Thanks for the help, I guess I'll do the init thing (unless they add a Created event or something in the future).

Here, I attached a cap of what I mean.

Basically, the function should affect objects from that family and make them flash. Left click makes a new green object and calls the function, which makes them all flash. Right click makes a new family object (which makes one from that family at random), and makes only that object flash. I'm pretty sure I know why it's doing this, but is there any way to have it both make just the one object flash and make it a specific type without looping through all of the objects already created?

Example Cap

Awesome, just what I was looking for! Thanks!

One problem with this, though: If you want this to be run for each new object created, it doesn't let you create a certain type of object and then have the function that deals with the family as a whole still only work with that one new object. It would let you do this if the function just dealt with one object type, so it's strange that you can't do this with families unless you want a random object from that family to be created each time. I'm pretty sure this is just how the object picker thing works, but it's still pretty weird.

I suppose you can create a variable and loop through them all looking for objects with that variable set to 0 or something, but that's kind of a weird way to do something like this.. (An On Create event or something would be pretty nice and solve quite a few problems like this, I think.)

Is there any way to do actions based on an object ID versus an object type? It seems strange that there are all these ways using "for each" and the like to loop using things like the solid attribute or object ID but you cannot actually do anything to the objects in these types of sets. This would be useful for doing the same actions to a few different types of objects without copying and pasting a bunch of code.. kind of like inheritance?

Am I just missing something? Or maybe there's a way to work around this that I haven't thought of?

Thanks!