Qualifiers

[Nifflas]

With the new qualifier update, it's more likely that one will fit the need, but I still run into situations where there's just not a working name. It would indeed be great if we could name them on our own and assign our own icons.

It's equally important that we'll also be able to name the alterable values of the qualifiers. I, as a principle, do not deal with unnamed variables, because the very idea of an unnamed variable in a language is something I can never understand, it's as alien as the idea about uncommented MMF2 events. By this reason, I always avoid qualifiers as much as I can. In one case when I wanted to set up an auto PMO assigner for multiple objects (example here) there was no way around this problem. Just check out how messy the code looks, despite that it's pretty much as nicely arranged as MMF2 events can get.

In Saira, I almost entierly worked my way around the need for qualifiers by making complex objects that would do lots of different things. I really wish I didn't have to do that though because the lack of "for each" I have to fastloop through all the objects, which eats too much CPU.

[variant]

That example is cool! There are ways around qualifiers like Nifflas said, you could do a variety of things to avoid them, like you can use the "Object is overlapping a backdrop" function.

-Variant

[nivram]

+1. I agree that it would be great to be able to name qualifiers.

Marv