MMF2 needs prober object selection

[Mathias]

Well, today I happily found out that you could make more MooGame objects in a single frame, so I could have multiple connections to a game I'm working for. I went on with having the objects created at runtime, and selecting them with the following expression:

Str(Fixed("MooGame")) - equal to - FixedValueStr

But instead of selecting the MooGame that has the fixed value eqaul to the FixedValueStr string, it selected all of the objects.
This have occured to me several times, even things besides MooGame, like Active objects, and I'm just getting tired of it.
Please Clickteam, or other people, get this sorted out! This is the only thing that makes it impossible for me to make games and whatever I want to make. I really liked the Select Object, but it is very limited to what I want to do.
Please!

[Corentin]

When you have such an expression, only the objects of the first parameter are looped through and selected. Only the first object of the second parmater is selected.

Try inverting your parameters :
FixedValue("object")=Counter
should work better.

Sorry I see my explanation is rather bad, but I can't explain better.

[Random]

Corentin is right. Only the object that "owns" the condition is considered for selection. So if you use "Compare general values" it will never select anything. Also if you use functions (in the expression editor) this will also never lead to a selection.
Functions always retrieve the values of one of the objects that you chose (like the one that was first created, or last, or whatever, don't count on it).

So DarkKiller, you should first understand how it works, before you complain that it doesn't work. But indeed, there should be more information about selection. Maybe I should write an article about it.

[Mathias]

I think I get it. So the advice Corentin gave me should work?

And Random, I never said it was broken. It just doest work the way I want it to work.

[Anders]

Imagine you have an expression in an extension that just returns the string "Cheese" and have around 10 instances of that extension in your app. Then if you compare two general values and compare a string object to that cheese expression, which objects would you expect would get selected?

The above made no sense to myself in many ways, I hope you get my point

[Mathias]

I get it, I get it...

But it would be great with more selection options. The Select Object made a huge improvement on this, but the only thing you can choose is the highest/lowest alterable value on Active Objects.
Also, this leads me to another question-

Is it MMF that selects the object or is it the object itself that decides which of the instances to use?

[Random]

Indeed, personally I also would like to see more ways for selecting objects. So I totally agree. But how it is right now, you can do more or less anything you want, it may just get complicated at some points.
So in the worst case you might for example have to do something like this, to get a selection:
*first
=> set flag 0 to false

*then
=> loop through all your objects

*on loop
+ check if the object is one of those that you want
=> set flag 0 to true

*on loop
+ conditions for more other objects you want to add to the selection
=> set flag 0 to true

*on loop
+ objects within the ones before that you DONT want in the selection
=> set flag 0 to false

*after loop
+if flag 0 is true
=> do stuff with it

Is it MMF that selects the object or is it the object itself that decides which of the instances to use?

In how far would that make a difference? You need to know which one to blame? I believe it's MMF that does the selections, but effectively it will be more intuitive if you assume that the object does the selection itself.

[Mathias]

Thanks for your reply, Random. But I already tried what you said there some time ago, I think it was the one version before the current. The frame was "cursed", as it didnt select the object probably, even when deleting the frame, creating it again, set everything to default, etc., but when I closed that application, and created a new one, it worked flawless. But I'm not sure if that's fixed now. I'll have a look at it later.
I sorted the thing with the MooGame object out by myself by using GFO and subapplications. Now I can create more MooGame connections at runtime. Woo!