getArray: Difference between revisions
Jump to navigation
Jump to search
m (add see also, categorized) |
Lou Montana (talk | contribs) m (Some wiki formatting) |
||
(103 intermediate revisions by 15 users not shown) | |||
Line 1: | Line 1: | ||
{{ | {{RV|type=command | ||
| | |game1= arma1 | ||
|version1= 1.00 | |||
|1.00 | |game2= arma2 | ||
|version2= 1.00 | |||
| | |game3= arma2oa | ||
|version3= 1.50 | |||
| | |game4= tkoh | ||
|version4= 1.00 | |||
| | |game5= arma3 | ||
|version5= 0.50 | |||
| | |gr1= Config | ||
| | |descr= Extract array from config entry. | ||
|s1= [[getArray]] config | |||
|p1= config: [[Config]] | |||
|r1= [[Array]] | |||
|x1= <sqf>_array = getArray (configFile >> "CfgVehicles" >> "Thing" >> "threat");</sqf> | |||
|seealso= [[configFile]] [[a / b]] [[configName]] [[count]] [[getText]] [[getNumber]] [[inheritsFrom]] [[isArray]] [[isClass]] [[isNumber]] [[isText]] [[select]] | |||
}} | }} | ||
< | {{Note | ||
< | |user= ffur2007slx2_5 | ||
< | |timestamp= 20140328075200 | ||
|text= ({{arma3}} 1.14) It's recommended to use [[BIS_fnc_getCfgData]] or [[BIS_fnc_returnConfigEntry]] to get variable cfg data rather than conditioning via [[isNumber]], [[isText]], [[isArray]], [[getNumber]], [[getText]] and [[getArray]] combination.<br> | |||
Traditional workaround: | |||
<sqf> | |||
_cfg = configFile >> "CfgVehicles" >> _SomeAddonClassName >> "DestructionEffects" >> "Smoke1" >> "type"; | |||
switch ( true ) do | |||
{ | |||
case (isNumber _cfg): {getNumber _cfg}; | |||
case (isText _cfg): {getText _cfg}; | |||
case (isArray _cfg): {getArray _cfg;}; | |||
default { nil }; | |||
}; | |||
</sqf> | |||
'''Recommended workaround:''' | |||
<sqf>(configFile >> "CfgVehicles" >> _SomeAddonClassName >> "DestructionEffects" >> "Smoke1" >> "type") call BIS_fnc_getCfgData;</sqf> | |||
To return default value once entry was not found, we can use [[BIS_fnc_returnConfigEntry]] instead of [[BIS_fnc_getCfgData]]. | |||
<sqf>[(configFile >> "CannonFire" >> "LightExp"),"lifeTime",0] call BIS_fnc_returnConfigEntry; // 0.5</sqf> | |||
}} | |||
< | {{Note | ||
</ | |user= demellion | ||
|timestamp= 20180112194800 | |||
|text= There is special behaviour if you try to read a description.ext config entry [[Array]] that contains a [[Boolean]].<br> | |||
Getting array in '''MP''' will result in [[Number]], while '''SP''' will return [[String]]. | |||
<sqf> | |||
// SP with false in array | |||
getArray (missionConfigFile >> "someClass" >> "someArray") // -> "false" | |||
// MP with false in array | |||
getArray (missionConfigFile >> "someClass" >> "someArray") // -> 0 | |||
</sqf> | |||
}} |
Latest revision as of 23:30, 13 May 2023
Description
- Description:
- Extract array from config entry.
- Groups:
- Config
Syntax
Examples
- Example 1:
Additional Information
- See also:
- configFile a / b configName count getText getNumber inheritsFrom isArray isClass isNumber isText select
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 28, 2014 - 07:52 (UTC)
-
(Arma 3 1.14) It's recommended to use BIS_fnc_getCfgData or BIS_fnc_returnConfigEntry to get variable cfg data rather than conditioning via isNumber, isText, isArray, getNumber, getText and getArray combination.
Traditional workaround:Recommended workaround:To return default value once entry was not found, we can use BIS_fnc_returnConfigEntry instead of BIS_fnc_getCfgData.(configFile >> "CfgVehicles" >> _SomeAddonClassName >> "DestructionEffects" >> "Smoke1" >> "type") call BIS_fnc_getCfgData;
- Posted on Jan 12, 2018 - 19:48 (UTC)
-
There is special behaviour if you try to read a description.ext config entry Array that contains a Boolean.
Getting array in MP will result in Number, while SP will return String.// SP with false in array getArray (missionConfigFile >> "someClass" >> "someArray") // -> "false" // MP with false in array getArray (missionConfigFile >> "someClass" >> "someArray") // -> 0
Categories:
- Scripting Commands
- Introduced with Armed Assault version 1.00
- ArmA: Armed Assault: New 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: Config