Bug - Spread Value

**Random** · 14th February 2007, 11:17 AM

Spread value # is buggy. If you spread a value for an object and start a loop in the same event, the spread value will happen AFTER the loop, no matter what.

Strangely, other events that don't particularly have to do with it can affect (and fix) it. See the following example file (2 frames, one with the problem, one with the strange behavior):

**Tiles** · 14th February 2007, 12:16 PM

Not a bug, but the way it works. A loop action in an event will be performed before everything else will be performed. And so it skips the spread value.

Therefore: spread value in another event BEFORE the line to start the fastloop. Both with just these actions.

**LIJI** · 14th February 2007, 12:31 PM

Incorrect.
A loop action will always run on time, the spread value action will always run last.

**Tiles** · 14th February 2007, 01:02 PM

Oookay ...

**Sphax** · 14th February 2007, 07:59 PM

So it could be known as a bug since this action don't do what it's supposed to do.

**Tiles** · 15th February 2007, 07:32 AM

Really? you need to spread value first when you want to use spreaded values in a fastloop, correct? And so you have to spread it first before starting the fastloop. No bug there. That you cannot do it in one event is another chapter. More a design issue than a bug ...

**Sphax** · 15th February 2007, 08:33 AM

Yes but MMF2 is supposed to do actions in the good order.

I know we can workaround but it's not what MMF2 is supposed to do.

Since some people ask "why this feature don't work correctly", it could be considerated as a bug, I think.

It's not a big problem of course so, it's not a big bug.

**Tiles** · 15th February 2007, 11:10 AM

Looking at it from this angle, agreed

**Random** · 16th February 2007, 05:54 PM

It's clearly a bug. It says nowhere that it works that way, and you should be able to deduce from similar actions how it is supposed to work (one action after the other, and not one of the at the end for no apparent reason).

The difference between a bug and a feature is that the feature is intended and documented as such.

Plus if you know "exactly" how MMF(2) events works but still have to spend some hours to figure this out, then it is not a positive feature aka a bug.

No offense Tiles, but stop defending this bug! :P