3 registered members (Ayumi, Akow, AndrewAMD),
1,505
guests, and 9
spiders. |
Key:
Admin,
Global Mod,
Mod
|
|
|
1 simple wait question
#451105
04/28/15 17:30
04/28/15 17:30
|
Joined: Apr 2005
Posts: 1,988 Canadian, Eh
DLively
OP
Serious User
|
OP
Serious User
Joined: Apr 2005
Posts: 1,988
Canadian, Eh
|
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
|
|
|
Re: 1 simple wait question
[Re: DLively]
#451106
04/28/15 17:36
04/28/15 17:36
|
Joined: Oct 2007
Posts: 5,210 İstanbul, Turkey
Quad
Senior Expert
|
Senior Expert
Joined: Oct 2007
Posts: 5,210
İstanbul, Turkey
|
God damn it. From the other thread: where you put your "wait" actually depends on what you are doing. 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.
3333333333
|
|
|
Re: 1 simple wait question
[Re: Quad]
#451113
04/28/15 18:40
04/28/15 18:40
|
Joined: May 2009
Posts: 5,370 Caucasus
3run
Senior Expert
|
Senior Expert
Joined: May 2009
Posts: 5,370
Caucasus
|
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.
Last edited by 3run; 04/28/15 18:49. Reason: me a bad guy once again
|
|
|
Re: 1 simple wait question
[Re: 3run]
#451115
04/28/15 18:54
04/28/15 18:54
|
Joined: Apr 2005
Posts: 1,988 Canadian, Eh
DLively
OP
Serious User
|
OP
Serious User
Joined: Apr 2005
Posts: 1,988
Canadian, Eh
|
Ironically, wrong was not the correct word. Placing 'wait' in most of your code/situation (which I've been noticing for a quiet a while) at the beginning of the loop is incorrect why is it wrong to put it at the top then???? All hail to the winner! grin Dingdingdingding 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...
Last edited by DLively; 04/28/15 18:55.
|
|
|
Re: 1 simple wait question
[Re: DLively]
#451116
04/28/15 18:57
04/28/15 18:57
|
Joined: May 2009
Posts: 5,370 Caucasus
3run
Senior Expert
|
Senior Expert
Joined: May 2009
Posts: 5,370
Caucasus
|
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 (even if they may be inccorect [thats learning baby]) Cheers!
|
|
|
Re: 1 simple wait question
[Re: 3run]
#451117
04/28/15 19:01
04/28/15 19:01
|
Malice
Unregistered
|
Malice
Unregistered
|
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.
|
|
|
Re: 1 simple wait question
[Re: 3run]
#451119
04/28/15 19:11
04/28/15 19:11
|
Joined: Apr 2005
Posts: 1,988 Canadian, Eh
DLively
OP
Serious User
|
OP
Serious User
Joined: Apr 2005
Posts: 1,988
Canadian, Eh
|
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 (even if they may be inccorect [thats learning baby]) Cheers! 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.
|
|
|
Re: 1 simple wait question
[Re: DLively]
#451122
04/28/15 20:47
04/28/15 20:47
|
Joined: Sep 2003
Posts: 9,859
FBL
Senior Expert
|
Senior Expert
Joined: Sep 2003
Posts: 9,859
|
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.
|
|
|
|