Printable View
From what I heard, I think a big part of the problem was that a qualifier could refer to one object type in one frame, and another object type in another, so referring to their actions globally would be impossible.
I've always suggested one solution to it - to always call qualifiers stuff like Bonus.Active or Collectables.String so that the object type always goes into the qualifier name.
I cant really ever imagine a situation like that coming up. For example, right now in my project I have Group.0 the entire group thats affected by my platform engine. I'm never going to put like a string or a counter in that group, I can't really think of a reason I'd want to...
Yeah, but the point is that your "Group.0" is actually "Group.0.Active" because all the objects in it are actives. In global events, MMF doesn't know what kind of objects are in the qualifier, so it has no idea whether your qualifier is "Group.0.Active" or "Group.0.String" or whatever.
If qualifiers were restricted to only one kind of object (eg active) at a whole-app level then it wouldn't be a problem.
But then I couln't do my game... :(Quote:
Originally Posted by Dynasoft