Can someone please explain this

Well it is the Qualifier:spread value 0 in alterable value H that is messing it up. In one frame the green one ends up with 0 and blue with 1 and in the other it's reversed. I think that when MMF spread values on qualifiers it will spread value in what order the objects were put on frame. Then, if there are more than one of any of the individual object, it will spread value based on their order on frame. So for example 2x ObjA and 3x ObjB both with qualifier Q1. If you place ObjB first on frame it will go like this.
ObjB1-0
ObjB2-1
ObjB3-2
ObjA1-3
ObjA2-4
If you place ObjA first then it will start with that and the values will be completely different.
And as far as I know there is no way to change that.

Quote from Outcast

I am having problems in my new app when I am copying all the objects and events over. Even if they are identical the result is different. I have isolated it down to an example, in one of the frames a text is placed at an y position and in the other frame it is not, even though there are exact same events and objects. I dont get it, does it have something to do with the id values?

Quote from BigHatLogan

Well it is the Qualifier:spread value 0 in alterable value H that is messing it up. In one frame the green one ends up with 0 and blue with 1 and in the other it's reversed. I think that when MMF spread values on qualifiers it will spread value in what order the objects were put on frame. Then, if there are more than one of any of the individual object, it will spread value based on their order on frame. So for example 2x ObjA and 3x ObjB both with qualifier Q1. If you place ObjB first on frame it will go like this.
ObjB1-0
ObjB2-1
ObjB3-2
ObjA1-3
ObjA2-4
If you place ObjA first then it will start with that and the values will be completely different.
And as far as I know there is no way to change that.

Display More

Don't spread values in qualifiers, and use a ForEach loop instead. Problem solved.

Quote from Outcast

Thanks, I have tried not to use ForEach since I found bugs with it in Flash runtime.

Clickteam has been working on fixing those bugs. It doesn't work at all in the Android runtime last time I checked, but it could already be fixed in both flash and android.

Quote from Outcast

When was the latest patch for it released? I am currently having bugs with using ForEach in my current project for flash (especially when using qualifiers). Also how do you even check what version of ForEach you have and where to retrieve the latest one? The latest one i see on the webpage linked in the object is from 2010 Please login to see this link.

Clickteam has been updating the ForEach object (which Clickteam seems to have the source code for) in the beta versions of MMF2 that have been released recently. If you aren't using the latest beta version of MMF2, then you don't have the latest version of the flash version of the ForEach object.

The latest flash build is 257.24 (though it doesn't seem like there have been any changes in the flash version since build 257.20), and the latest normal version (which still will update to flash build 257.24) is build 257.30.

Quote from Outcast

Hm if there have been no changes it is not worth trying to update?

I said it doesn't seem like there are any changes. One version didn't have a change log, though some changes might have been made anyway. It's definitely worth updating to build 257.30 anyway since it makes some bug fixes/changes outside of the Flash runtime.

There has been changes by both Francois and FVivolo on ForEach for flash irrc. Update to the latest flash beta.

Strange, what is/are the bugs? ForEach works with qualifiers on my end...

I'll check up and see what happened. I know Francois did some changes to ForEach (or maybe FVivolo) on two separate occasions, so it did used to work and the object I have does but maybe it wasn't thrown into the wild yet...