BIS fnc spawnOrdered: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "<!--|serverExec= server-->" to "") |
m (added group) |
||
| Line 5: | Line 5: | ||
|version1= 1.96 | |version1= 1.96 | ||
|gr1 = Program Flow | |||
|descr= Spawns given function and executes it in the order it was called in case multiple calls are made. If mutex name is not specified, function name is used. | |descr= Spawns given function and executes it in the order it was called in case multiple calls are made. If mutex name is not specified, function name is used. | ||
Revision as of 20:10, 18 January 2021
Description
- Description:
- Spawns given function and executes it in the order it was called in case multiple calls are made. If mutex name is not specified, function name is used.
- Execution:
- call
- Groups:
- Program Flow
Syntax
- Syntax:
- [params, functionName, mutexName] call BIS_fnc_spawnOrdered
- Parameters:
- params: Anything - Function params
- functionName: String - Function name in current namespace
- mutexName: String - (Optional, default functionName) This is a reference to group of spawns. It's saved in the missionNamespace variable BIS_fnc_spawnOrdered_mutexName
- Return Value:
- Boolean - Returns false if function name is empty, otherwise true
Examples
- Example 1:
myFnc = { diag_log [_this, canSuspend] }; for "_i" from 0 to 1000 do { [_i, "myFnc"] call BIS_fnc_spawnOrdered };
Additional Information
- See also:
- spawn
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