spawn: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Some wiki formatting) |
Lou Montana (talk | contribs) m (Text replacement - "Nelis.75733126" to "Nelis75733126") |
||
(7 intermediate revisions by 3 users not shown) | |||
Line 25: | Line 25: | ||
Therefore [[spawn]] does not wait for the supplied code to finish, instead, [[spawn]] returns a [[Script Handle|Script]] handle to the [[Scheduler|scheduler]] task. | Therefore [[spawn]] does not wait for the supplied code to finish, instead, [[spawn]] returns a [[Script Handle|Script]] handle to the [[Scheduler|scheduler]] task. | ||
[[scriptDone]] command can be used to check the code completion. Additional arguments are passed to the code in local variable [[Magic Variables#this|_this]]. | [[scriptDone]] command can be used to check the code completion. Additional arguments are passed to the code in local variable [[Magic Variables#this|_this]]. | ||
Since {{GVI|arma3|1.56|size=0.75}} the script handle also exists inside the code in {{hl|_thisScript}} variable. | Since {{GVI|arma3|1.56|size= 0.75}} the script handle also exists inside the code in {{hl|_thisScript}} variable. | ||
To see what spawned scripts are currently in the scheduler, use [[diag_activeSQFScripts]] command. | To see what spawned scripts are currently in the scheduler, use [[diag_activeSQFScripts]] command. | ||
{{Feature|warning| When multiple [[Code]] is [[spawn]]ed in an order, there is <u>no guarantee</u> that the [[spawn]]ed [[Code]] will execute in the same order (see {{ | {{Feature|warning| When multiple [[Code]] is [[spawn]]ed in an order, there is <u>no guarantee</u> that the [[spawn]]ed [[Code]] will execute in the same order (see {{Link|#Example 2}}). If the order is important, use [[BIS_fnc_spawnOrdered]].}} | ||
|s1= arguments [[spawn]] code | |s1= arguments [[spawn]] code | ||
Line 92: | Line 92: | ||
|user= DreadedEntity | |user= DreadedEntity | ||
|timestamp= 20141021233300 | |timestamp= 20141021233300 | ||
|text= [[spawn]] requires a script handle when used in the 2D | |text= {{GVI|arma3|0.50}} [[spawn]] requires a script handle when used in the [[Editor|2D-Editor]].</br> | ||
In scripts and in the debug console, it is not required, but very useful for keeping track of running scripts. Having a script handle also makes it easy to [[terminate]] scripts at any time.<br><br> | {{GVI|arma3|2.04}} In [[:Category:Eden Editor|Eden Editor]] this is no longer necessary.</br></br> | ||
In scripts and in the [[Arma 3: Debug Console| debug console]], it is not required, but very useful for keeping track of running scripts. Having a script handle also makes it easy to [[terminate]] scripts at any time.</br></br> | |||
Since [[spawn]] creates a new [[Scheduler#Scheduled_Environment|scheduled environment]], having an excess of open [[Scheduler#Threads|threads]] can make the [[Scheduler#Scheduler|scheduler]] queue extremely long, significantly increasing the execution time of each [[Scheduler#Threads|thread]]. (it takes an extremely large amount of [[Scheduler#Threads|threads]], though) | Since [[spawn]] creates a new [[Scheduler#Scheduled_Environment|scheduled environment]], having an excess of open [[Scheduler#Threads|threads]] can make the [[Scheduler#Scheduler|scheduler]] queue extremely long, significantly increasing the execution time of each [[Scheduler#Threads|thread]]. (it takes an extremely large amount of [[Scheduler#Threads|threads]], though) | ||
}} | }} | ||
{{Note | {{Note | ||
|user= | |user= Nelis75733126 | ||
|timestamp= 20150825133900 | |timestamp= 20150825133900 | ||
|text= If you | |text= If you have a local (private) function that you want to access from within code created with <sqf inline>spawn</sqf>, you can pass that private function to the code of <sqf inline>spawn</sqf>, like so: | ||
<sqf> | <sqf> | ||
_someFunction = {}; | |||
[ _someFunction ] spawn { call( _this select 0 ) }; | |||
</sqf> | </sqf> | ||
}} | }} |
Latest revision as of 15:38, 29 June 2024
Description
- Description:
- Adds given set of compiled instructions to the scheduler. Exactly when the code will be executed is unknown, it depends on how busy is the engine and how filled up is the scheduler. Therefore spawn does not wait for the supplied code to finish, instead, spawn returns a Script handle to the scheduler task. scriptDone command can be used to check the code completion. Additional arguments are passed to the code in local variable _this. Since 1.56 the script handle also exists inside the code in _thisScript variable. To see what spawned scripts are currently in the scheduler, use diag_activeSQFScripts command.
- Groups:
- Program Flow
Syntax
- Syntax:
- arguments spawn code
- Parameters:
- arguments: Anything - arguments passed to the script, which later available in _this variable inside the script.
- code: Code
- Return Value:
- Script Handle - can be used to determine (via scriptDone (also via isNull in Arma 3)) when the spawned script has finished. In Arma 3, the handle is also available inside the spawned script in _thisScript variable
Examples
- Example 1:
- Example 2:
- There is no guarantee that spawned scripts will be executed in the same order they spawned:
- Example 3:
- Local variables declared in the main scope are not available in the spawned code. You have to pass them as parameters:
private _localVariable = 1234; [_localVariable] spawn { systemChat format ["_localVariable does not exist: %1", isNil "_localVariable"]; // _localVariable does not exist: true params ["_localVariable"]; systemChat format ["_localVariable is now: %1", _localVariable]; // _localVariable is now: 1234 };
Additional Information
- See also:
- call execVM execFSM exec compile preprocessFileLineNumbers preprocessFile terminate scriptDone remoteExec sleep uiSleep canSuspend
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on Mar 06, 2009 - 00:20 (UTC)
-
spawn cannot call other local functions on the same scope as itself.
It can, however, call other global functions: The call of _addOne from the spawned function does not do anything.
- Posted on Oct 21, 2014 - 23:33 (UTC)
-
0.50 spawn requires a script handle when used in the 2D-Editor.
2.04 In Eden Editor this is no longer necessary.
In scripts and in the debug console, it is not required, but very useful for keeping track of running scripts. Having a script handle also makes it easy to terminate scripts at any time.
Since spawn creates a new scheduled environment, having an excess of open threads can make the scheduler queue extremely long, significantly increasing the execution time of each thread. (it takes an extremely large amount of threads, though)
- Posted on Aug 25, 2015 - 13:39 (UTC)
- If you have a local (private) function that you want to access from within code created with spawn, you can pass that private function to the code of spawn, like so:
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint: Elite version 1.00
- Operation Flashpoint: Elite: New Scripting Commands
- Operation Flashpoint: Elite: Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Program Flow