How come it's not possible to use qualifier objects in the global events?
Printable View
How come it's not possible to use qualifier objects in the global events?
How come it's not possible to use qualifier objects in the global events?
Francois stated the reasons in this post back in 2003:
[]Use of qualifiers in global and local objects : no it is impossible. To define an event, I need to know in advance the type of the object used by the event (being an active, counter, string etc). In a global event list, I cannot predict the type, so the event is defined with one type and may not work in some of the frames. I do not think it will be possible to change that in MMF2.[/]
Francois stated the reasons in this post back in 2003:
[]Use of qualifiers in global and local objects : no it is impossible. To define an event, I need to know in advance the type of the object used by the event (being an active, counter, string etc). In a global event list, I cannot predict the type, so the event is defined with one type and may not work in some of the frames. I do not think it will be possible to change that in MMF2.[/]
Never mind, It's been asked before on the forums, I didn't look close enough
Edit: Jup, thanks Joshtek
Never mind, It's been asked before on the forums, I didn't look close enough
Edit: Jup, thanks Joshtek
It just needs a simple editor under "application properties" to bind qualifiers to object types (from the Insert Object list) globally. Then don't allow an object to have a qualifier that has been bound to a different type, and don't allow unbounded qualifiers in global events. MMF's power would be greatly increased....
It just needs a simple editor under "application properties" to bind qualifiers to object types (from the Insert Object list) globally. Then don't allow an object to have a qualifier that has been bound to a different type, and don't allow unbounded qualifiers in global events. MMF's power would be greatly increased....
[]It just needs a simple editor under "application properties" to bind qualifiers to object types (from the Insert Object list) globally. Then don't allow an object to have a qualifier that has been bound to a different type, and don't allow unbounded qualifiers in global events. MMF's power would be greatly increased.... [/]
Or when you add a qualifier you select the object type, and then those specific actions will only affect objects of that qualifier and object type (e.g. qualifier.button.hud or qualifier.hud.button)
[]It just needs a simple editor under "application properties" to bind qualifiers to object types (from the Insert Object list) globally. Then don't allow an object to have a qualifier that has been bound to a different type, and don't allow unbounded qualifiers in global events. MMF's power would be greatly increased.... [/]
Or when you add a qualifier you select the object type, and then those specific actions will only affect objects of that qualifier and object type (e.g. qualifier.button.hud or qualifier.hud.button)
Yeah... actually MMF is already set up to do that. Try making an Active and a String, then assign them the same qualifier. The event editor automatically splits it into two groups, exactly as you describe, Group.Player.Sprite and Group.Player.String. I'm afraid I can't see why the Global events couldn't do that, if that's the only issue.
Yeah... actually MMF is already set up to do that. Try making an Active and a String, then assign them the same qualifier. The event editor automatically splits it into two groups, exactly as you describe, Group.Player.Sprite and Group.Player.String. I'm afraid I can't see why the Global events couldn't do that, if that's the only issue.