Printable View
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):
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.
Incorrect.
A loop action will always run on time, the spread value action will always run last.
Oookay ... XD
So it could be known as a bug since this action don't do what it's supposed to do. ;)
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 ... ;)
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.
Looking at it from this angle, agreed :)
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
Can't it just be a quirk?
it might be easier if we divided the term "BUG" into two groups:
1. Insects
2. Arachnids
That way, we can tell how to handle the bug.
lol Joshtek :)
Sorry for the delay, I was on holidays last week.
This is not a bug, this is how the action routines are coded. I perform several loops of actions. The first exploration of the actions, calls all the actions, including the one shot actions like loops, sound etc., and the object oriented actions for the first object to be explored.
Then the next loops explores the remaining object oriented actions for the other objects, including the spread actions.
So if you want your spread action to be executed before, just duplicate the line of events.
Maybe such actions should be denoted in a special way (e.g. like true events, in another color), or should always move to the end of the list of events or anything like that to make troubleshooting easier.
Btw - why is it possible at all to put true events in a line different than the first? Wouldn't it make sense to restrict that?
There are times where you might want to wait for it to be dealt with in the normal course of events instead of straight away.Quote:
Originally Posted by Random
Oh sorry. That's not what I meant. I mean.. why can you do this:
+ Active is in the play area
+ User clicks with left mouse button
-> add 1 to counter A
Correct would be
[color:#FF0000]+ User clicks with left mouse button[/color]
+ Active is in the play area
-> add 1 to counter B
EDIT:
with the first one you get undesired results. Try it. Put an AO in a new frame and add two counters. Then add the above events.
When you run the app, you will see the first counter goes 1 up immediately, without even clicking. So why would you ever want that, or why would you want to let beginners run into a problem like this?
Sorry I'm not going to contribute anything here, bur rather ask a question : is there an article or tutorial that explains just what spreading values means and what benefits the developer can get from using it. I'm a basic clicker !
Thanks for your help ,
Eric
irregularstuff.com
Spread value
This action is quite powerful and allows you to spread numbers in an alterable value of multiple instances of an object. Imagine you have 10 instances of an object called "Ball". If you spread a value in Alterable Value A of the Ball object, starting at 1, the first object will have the value 1, the second the value 2, the third 3 etc. up to 10.
(from the program Help)
Too bad the clickwiki is down right now (www.clickwiki.info). You can find many of these questions answered there.
I suppose the next question would be "what is an instance?" ;)
If you follow the Chocobreak tutorial to make a breakout-style game you have to add many bricks to your frame. In fact, you only have one "brick" object, but multiple instances of it. This means you only have to have one "ball collides with brick" event, which applies to all of the Brick objects on screen.Quote:
I suppose the next question would be "what is an instance?" ;)
thanks for your answers !!