configProperties: Difference between revisions

Revision as of 00:31, 7 February 2021

Game1 needed - Version1 needed

Hover & click on the images for description

Description:: This article is a Stub. You can help BI Community Wiki by expanding it.
Description needed
Groups:: Config

Syntax:: Syntax needed
Parameters:: [config, condition, inherit]: Array
: config: Config - config entry to search
: condition (Optional): String - expression, which if returns true, adds current property to result. Default: "true"
: inherit (Optional): Boolean - include inherited properties. Default: true
Return Value:: Return value needed

Example 1:: _configs = configProperties [configFile >> "CfgVehicles" >> "O_Truck_02_box_F"];
Example 2:: _configs = configProperties [configFile >> "RscText", "true", true];
Example 3:: Get all hitpoints of a truck:_hitPoints = []; _hitPointsCfgs = configProperties [ configFile >> "CfgVehicles" >> "O_Truck_02_box_F" >> "HitPoints", "true", true ]; hint str _hitPointsCfgs;

: 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

@@ Line 8: / Line 8: @@
 |  Returns an array of config entries which meet criteria in condition code. Command iterates through available classes and config properties for given config entry. If 3rd param is [[true]] the search also includes inherited properties. Current looked at config is stored in _x variable (similar to alternative [[count]] command implementation). Condition has to return [[true]] in order for the looked at property to be added to the resulting array. A bit slower than [[configClasses]] but allows to access inherited entries.
-<br><br>{{Feature|$Warning| The condition code passed to [[configProperties]] should only be used for '''simple filter expressions''' and nothing more}}
+<br><br>{{Feature|Warning| The condition code passed to [[configProperties]] should only be used for '''simple filter expressions''' and nothing more}}
 {{Feature|Informative|With {{arma3}} 2.01.147002 the following conditions were optimised inside the engine:
 * <tt>"true" </tt> (condition omitted)