spawn - Revision history

Dedmen: spawn without arguments and Promises

2025-07-10T15:33:35Z

spawn without arguments and Promises

← Older revision		Revision as of 17:33, 10 July 2025
Line 37:		Line 37:

	\|r1= [[Script Handle]] - can be used to determine (via [[scriptDone]] (also via [[isNull]] in {{arma3}})) when the spawned script has finished. In {{arma3}}, the handle is also available inside the spawned script in {{hl\|_thisScript}} variable		\|r1= [[Script Handle]] - can be used to determine (via [[scriptDone]] (also via [[isNull]] in {{arma3}})) when the spawned script has finished. In {{arma3}}, the handle is also available inside the spawned script in {{hl\|_thisScript}} variable


			\|s2= [[spawn]] code
			\|s2since= arma3 2.22
			\|p21= code: [[Code]]
			\|r2= [[Script Handle]]


			\|s3= [[spawn]] name
			\|s3since= arma3 2.22
			\|p41= name: [[String]] - The name of a "Empty Handle". Behaves like [[scriptName]] inside a function.
			\|r3= [[Script Handle]] - A "Empty Handle" to be used as a [[Script_Handle#Promise_Handles\|Promise]]





	\|x1= <sqf>_handle = 0 spawn { player globalChat "Hello world!" };</sqf>		\|x1= <sqf>_handle = 0 spawn { player globalChat "Hello world!" };</sqf>

Lou Montana: Text replacement - "''via''" to "via"

2025-02-21T10:44:30Z

Text replacement - "''via''" to "via"

← Older revision		Revision as of 12:44, 21 February 2025
Line 36:		Line 36:
	\|p2= code: [[Code]]		\|p2= code: [[Code]]

	\|r1= [[Script Handle]] - can be used to determine (''via'' [[scriptDone]] (also via [[isNull]] in {{arma3}})) when the spawned script has finished. In {{arma3}}, the handle is also available inside the spawned script in {{hl\|_thisScript}} variable		\|r1= [[Script Handle]] - can be used to determine (via [[scriptDone]] (also via [[isNull]] in {{arma3}})) when the spawned script has finished. In {{arma3}}, the handle is also available inside the spawned script in {{hl\|_thisScript}} variable

	\|x1= <sqf>_handle = 0 spawn { player globalChat "Hello world!" };</sqf>		\|x1= <sqf>_handle = 0 spawn { player globalChat "Hello world!" };</sqf>

Lou Montana: Text replacement - " ''via'' " to " via "

2025-02-21T10:44:04Z

Text replacement - " ''via'' " to " via "

← Older revision		Revision as of 12:44, 21 February 2025
Line 36:		Line 36:
	\|p2= code: [[Code]]		\|p2= code: [[Code]]

	\|r1= [[Script Handle]] - can be used to determine (''via'' [[scriptDone]] (also ''via'' [[isNull]] in {{arma3}})) when the spawned script has finished. In {{arma3}}, the handle is also available inside the spawned script in {{hl\|_thisScript}} variable		\|r1= [[Script Handle]] - can be used to determine (''via'' [[scriptDone]] (also via [[isNull]] in {{arma3}})) when the spawned script has finished. In {{arma3}}, the handle is also available inside the spawned script in {{hl\|_thisScript}} variable

	\|x1= <sqf>_handle = 0 spawn { player globalChat "Hello world!" };</sqf>		\|x1= <sqf>_handle = 0 spawn { player globalChat "Hello world!" };</sqf>

Lou Montana: Text replacement - "Nelis.75733126" to "Nelis75733126"

2024-06-29T14:38:30Z

Text replacement - "Nelis.75733126" to "Nelis75733126"

← Older revision		Revision as of 16:38, 29 June 2024
Line 99:		Line 99:

	{{Note		{{Note
	\|user= ~~Nelis.75733126~~		\|user= Nelis75733126
	\|timestamp= 20150825133900		\|timestamp= 20150825133900
	\|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:		\|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:

Nelis75733126: made my note a bit more friendly to newcomers. or at least, i tried :)

2024-04-16T18:46:03Z

made my note a bit more friendly to newcomers. or at least, i tried :)

← Older revision		Revision as of 20:46, 16 April 2024
Line 101:		Line 101:
	\|user= Nelis.75733126		\|user= Nelis.75733126
	\|timestamp= 20150825133900		\|timestamp= 20150825133900
	\|text= If you ~~want to call~~ a local function ~~which has NOT been~~ created ~~inside a spawned~~ function, ~~then do this~~:		\|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>
	~~_fncOne~~ = { ~~systemChat "This is _fncOne"~~ };		_someFunction = {};
	~~_fncTwo =~~ { call (_this select 0) };		[ _someFunction ] spawn { call( _this select 0 ) };
	~~[_fncOne] spawn _fncTwo~~;
	</sqf>		</sqf>
	}}		}}

Lou Montana: Text replacement - "IT07" to "Nelis.75733126"

2024-04-16T17:00:15Z

Text replacement - "IT07" to "Nelis.75733126"

← Older revision		Revision as of 19:00, 16 April 2024
Line 99:		Line 99:

	{{Note		{{Note
	\|user= ~~IT07~~		\|user= Nelis.75733126
	\|timestamp= 20150825133900		\|timestamp= 20150825133900
	\|text= If you want to call a local function which has NOT been created inside a spawned function, then do this:		\|text= If you want to call a local function which has NOT been created inside a spawned function, then do this:

Lou Montana: Text replacement - ":Category:Eden Editor" to "Eden Editor"

2023-07-09T12:26:41Z

Text replacement - "Category:Eden Editor" to "Eden Editor"

← Older revision		Revision as of 14:26, 9 July 2023
Line 93:		Line 93:
	\|timestamp= 20141021233300		\|timestamp= 20141021233300
	\|text= {{GVI\|arma3\|0.50}} [[spawn]] requires a script handle when used in the [[Editor\|2D-Editor]].</br>		\|text= {{GVI\|arma3\|0.50}} [[spawn]] requires a script handle when used in the [[Editor\|2D-Editor]].</br>
	{{GVI\|arma3\|2.04}} In [[:Category:Eden Editor]] this is no longer necessary.</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>		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)

Lou Montana: Text replacement - "\[\[Eden( |_)Editor(\||\])" to "[[:Category:Eden Editor$2"

2023-07-09T12:21:03Z

Text replacement - "\[\[Eden( |_)Editor(\||\])" to "[[:Category:Eden Editor$2"

← Older revision		Revision as of 14:21, 9 July 2023
Line 93:		Line 93:
	\|timestamp= 20141021233300		\|timestamp= 20141021233300
	\|text= {{GVI\|arma3\|0.50}} [[spawn]] requires a script handle when used in the [[Editor\|2D-Editor]].</br>		\|text= {{GVI\|arma3\|0.50}} [[spawn]] requires a script handle when used in the [[Editor\|2D-Editor]].</br>
	{{GVI\|arma3\|2.04}} In [[Eden Editor]] this is no longer necessary.</br></br>		{{GVI\|arma3\|2.04}} In [[:Category: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>		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)

R3vo: updated note

2023-06-24T22:18:05Z

updated note

← Older revision		Revision as of 00:18, 25 June 2023
Line 92:		Line 92:
	\|user= DreadedEntity		\|user= DreadedEntity
	\|timestamp= 20141021233300		\|timestamp= 20141021233300
	\|text= [[spawn]] requires a script handle when used in the 2D ~~editor~~. ~~'''(A3)'''~~<br>		\|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 [[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)
	}}		}}

Lou Montana: Text replacement - "|size=0.75" to "|size= 0.75"

2022-12-21T11:09:39Z

Text replacement - "|size=0.75" to "|size= 0.75"

← Older revision		Revision as of 13:09, 21 December 2022
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.

← Older revision		Revision as of 14:26, 9 July 2023
Line 93:		Line 93:
	\|timestamp= 20141021233300		\|timestamp= 20141021233300
	\|text= {{GVI\|arma3\|0.50}} [[spawn]] requires a script handle when used in the [[Editor\|2D-Editor]].</br>		\|text= {{GVI\|arma3\|0.50}} [[spawn]] requires a script handle when used in the [[Editor\|2D-Editor]].</br>
	{{GVI\|arma3\|2.04}} In [[:Category:Eden Editor]] this is no longer necessary.</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>		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)

← Older revision		Revision as of 14:21, 9 July 2023
Line 93:		Line 93:
	\|timestamp= 20141021233300		\|timestamp= 20141021233300
	\|text= {{GVI\|arma3\|0.50}} [[spawn]] requires a script handle when used in the [[Editor\|2D-Editor]].</br>		\|text= {{GVI\|arma3\|0.50}} [[spawn]] requires a script handle when used in the [[Editor\|2D-Editor]].</br>
	{{GVI\|arma3\|2.04}} In [[Eden Editor]] this is no longer necessary.</br></br>		{{GVI\|arma3\|2.04}} In [[:Category: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>		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)