Controlling program flow – Talk
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
::perhaps, but those commands refer to [[Script]] and not [[Functions_-_SQF]]. Indeed, [[sleep]] and [[waitUntil]] are given as examples of script-only instructions. [[User:Dinger|Dinger]] 09:38, 24 July 2006 (CEST) | ::perhaps, but those commands refer to [[Script]] and not [[Functions_-_SQF]]. Indeed, [[sleep]] and [[waitUntil]] are given as examples of script-only instructions. [[User:Dinger|Dinger]] 09:38, 24 July 2006 (CEST) | ||
:::Changes made to add functions everywhere ;) So it's not script-only. [[User:Whisper|Whisper]] 11:15, 24 July 2006 (CEST) | |||
Revision as of 10:15, 24 July 2006
Scripts are deprecated?
I seem to recall having a discussion at the MAPFACT meeting where, in fact, it was acknowledged that scripts were still valid. Does this mean that there are now function commands to pause executing of an .sqf file? The example of an .sqf shows this problem as, A) A WHILE loop executes in the same slice, while the "refueling script" has a half-second delay built it. B) the last I checked, .sqf lines need a semicolon at the end.Dinger 09:38, 24 July 2006 (CEST)
- Just look for sleep-command :), at least that's my understanding of the new Scripting engine; there also things like spawn, which seem to be predestined for asynchronous script execution. --Vektorboson 18:22, 23 July 2006 (CEST)
- perhaps, but those commands refer to Script and not Functions_-_SQF. Indeed, sleep and waitUntil are given as examples of script-only instructions. Dinger 09:38, 24 July 2006 (CEST)
- Changes made to add functions everywhere ;) So it's not script-only. Whisper 11:15, 24 July 2006 (CEST)