I have an event that makes all the active objects with the qualifier "player" disappear and it works. However I have another event which tells these active objects to disappear when I click on one of them and instead of all the qualified active objects diappearing as they should only one of the sonofaguns disappears the rest just sit there and stare stupidly at me on the frame refusing to disappear! I swear I would shoot them but that would ruin my monitor. When I remove the qualifier from one of them the other suddenly disappears when the event is triggered. Other wierd things have been happening. In the middle of nowhere my mmf application will just disappear from the screen and all my unsaved work is lost. Sometimes I will try to add an event or a formula and there is a delay as the screen comes on partialy. Maybe I should mention the strange voices that I have been hearing that know one else seems to hear but I promise that only started after my mmf started to act wacko. Also for some strange reason if I try to save an associative array in a fastloop the application crashes. All this started when I switched to windows xp sp2 on my brand new computer. I scanned my computer with norton anti virus but thankfuly nothing turned up!
qualifiers seem to have always been buggy. Such as you can't use spread alterable value in it, use them in global events, so it wouldn't suprise me if actions didn't effect every object with the qualifier.
As a boy, I wanted to be a train. I didn’t realize this was unusual—that other kids played with trains, not as them.
I suppose it's possible that Service Pack 2 is to blame for some of the crashes, as while it works for some, it seems to mess up some people's computers irredeemably (mine included).
Lots of people seem to say qualifiers don't work properly. They DO! They work perfectly. Spreading alterable values in qualifiers works as well. I use qualifiers on a massive scale on Terminal Orbit, with absolutely no problems. In fact the whole engine relies on values being spread in qualifier alterable values.
If your event looks like this:
+ User clicks on "Group Good"
: Group good: Destroy
Then the fact only one object is destroyed is actually a useful feature of MMF. Only objects which apply to the event's conditions have the actions done on them. So only the object you clicked on is destroyed. In fact this is such a critical functionality of MMF that if it didnt work like this it would be a pretty useless program.
To work around:
+ User clicks on "Group Good"
: Set global value A (or some counter) to 1
+ Global value A = 1
: Destroy Group.Good
: Set global value A to 0
Because no objcts specifically apply to the second event, MMF destroys all of them.
To say the least, I never had a problem with WindowsXP SP2, not sure why most people are. I actually like SP2 better, example, little sheild comes up when I turn my firewall off & forgot to turn it back on. Really useful addition for me. About system restore, best thing I found Microsoft add to Windows, not sure when they added it nor do I care, all's I know is that feature has saved my computer's butt alot!
I hate it just for that reason brandon , I don't like it wasting my precious system tray space, and disableing the system tray is not an easy task, well, it is, but you have to restart the computer when you change that setting
As a boy, I wanted to be a train. I didn’t realize this was unusual—that other kids played with trains, not as them.
Qualifiers work fine in TGF, I've never had a problem. They aren't all powerful, there is certain obvious limitations that you just have to take into account.
thinking is like pong, it's easy, but you miss sometimes.
TGF qualifiers can be buggy or limited, e.g. if you try to create an object at 0,0 from a qualifier in TGF, it doesn't work. In MMF, you can do it and it does work.
Advertisement
Post Reply
Edited by the Author.
, I don't like it wasting my precious system tray space, and disableing the system tray is not an easy task, well, it is, but you have to restart the computer when you change that setting 
