getArray: Difference between revisions
No edit summary |
(Add BIS_fnc_returnConfigEntry as an enhanced fnc to bis_fnc_getcfgdata) |
||
| Line 29: | Line 29: | ||
<dd class="notedate">Posted on Mar 28, 2014 - 07:48 | <dd class="notedate">Posted on Mar 28, 2014 - 07:48 | ||
<dt class="note">'''[[User:ffur2007slx2_5|ffur2007slx2_5]]'''<dd class="note"> | <dt class="note">'''[[User:ffur2007slx2_5|ffur2007slx2_5]]'''<dd class="note"> | ||
In ArmA3 ver 1.14, it is recommended to use [[BIS_fnc_GetCfgData]] to get variable cfg data rather than conditioning via [[isNumber]], [[isText]], [[isArray]], [[getNumber]], [[getText]] and [[getArray]] combination. E.g.<br> | In ArmA3 ver 1.14, it is 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. E.g.<br> | ||
Traditional workaround: | Traditional workaround: | ||
<code> | <code> | ||
| Line 44: | Line 44: | ||
<code> | <code> | ||
(configfile >> "CfgVehicles" >> _SomeAddonClassName >> "DestructionEffects" >> "Smoke1" >> "type") call bis_fnc_getcfgdata; | (configfile >> "CfgVehicles" >> _SomeAddonClassName >> "DestructionEffects" >> "Smoke1" >> "type") call bis_fnc_getcfgdata; | ||
</code> | |||
To return default value once entry was not found, we can use [[BIS_fnc_returnConfigEntry]] instead of [[bis_fnc_getcfgdata]]. e.g. | |||
<code> | |||
[(configfile >> "CannonFire" >> "LightExp"),"lifeTime",0] call BIS_fnc_returnConfigEntry;//0.5 | |||
</code> | </code> | ||
<!-- Note Section END --> | <!-- Note Section END --> | ||
Revision as of 09:35, 3 April 2014
Description
- Description:
- Extract array from config entry.
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
_array = getArray (configFile >> "CfgVehicles" >> "Thing" >> "threat")
Additional Information
- See also:
- configFileconfig/nameconfigNamecountgetTextgetNumberinheritsFromisArrayisClassisNumberisTextselect
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
Notes
- Posted on Mar 28, 2014 - 07:48
- ffur2007slx2_5
-
In ArmA3 ver 1.14, it is 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. E.g.
Traditional workaround:_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}; };Recommended workaround:(configfile >> "CfgVehicles" >> _SomeAddonClassName >> "DestructionEffects" >> "Smoke1" >> "type") call bis_fnc_getcfgdata;To return default value once entry was not found, we can use BIS_fnc_returnConfigEntry instead of bis_fnc_getcfgdata. e.g.[(configfile >> "CannonFire" >> "LightExp"),"lifeTime",0] call BIS_fnc_returnConfigEntry;//0.5