To the point.

I place my waits after the first curly bracker in a while loop.
There is controversy on this topic and I'd like to know from the developers brain why a wait should be at the end of any while loop (be it in an action or function)

thank you

God damn it.

From the other thread:


Right place to put wait depends on what you are doing and how you are doing it. You could be putting it in the middle of the loop and doing the right thing.

why is it wrong to put it at the top then????

it is not.

All hail to the winner! Dingdingdingding

Edit: Ok, sorry. I don't really want to act like a jackass. I probably was wrong, so sorry.

Ironically, wrong was not the correct word.










I just don't understand Why 3runs complaining that my wait is at the top of my while loop..

@3run: why did you make a big deal out of it -- You tell me its wrong but don't tell me why? Everyone else says you're wrong...

I can only quote something from your previous thread


Cheers!

This is a non-point. You starting with a wait(1) COULD cause issue. You don't care or want a list of the issue. Do what ever you feel like if it works. Right or wrong, simple or elegant. This is such a non-point. It should have been dropped by now, not posted here.

Fair enough. Im glad we are back on the same page as before all this shit.. ( I hope we can both be mature about this )

@Malice: there comes a point in development were everything means something -- Especially If it will cause an issue later on (Big enough that I need to worry about) I'd like to be aware of it now, and not have any surprises -- even as simple as a wait.

I finished one game using the latter method with no bad results, so that's why I'm curious about it..
I leave the ultimate answer to this question in the capable hands of the developers



#WowGladThatsOver.

Cheers.

The point why you USUALLY don't put a wait(1) on top is, that normally you want to have the very first run of the loop completed immediately (e.g. directly after entity creation) so any changes you do affect (the entity) direectly.

If you put a wait(1) on top of the loop, you will have one frame delay on first run, which can cause a short "jitter" when modifying position, scale, alpha of the entity in the loop. As long as the loop has not run at least once, you'll see the old/default values, which may be entirely different.

That's all to it.
When not doing entity stuff, wait(1) on top might be just what you want. There isn't really a right or wrong.