Misc. - Replace configProperties wherever possible#11265
Misc. - Replace configProperties wherever possible#11265PabstMirror merged 12 commits intomasterfrom
configProperties wherever possible#11265Conversation
| @@ -18,8 +18,9 @@ | |||
|
|
|||
| private _currentWeapon = currentWeapon ACE_player; | |||
| if !(GVAR(launcherWeapons) getOrDefaultCall [_currentWeapon, { | |||
There was a problem hiding this comment.
Might even be able to remove the cache, as it's quite quick.
|
I think at this point I'll come up with a test suite for checking the difference between |
* Code cleanup * Revert _ammo changes * Update fnc_onFiredGetArgs.sqf
|
2.22 will add a syntax for https://community.bistudio.com/wiki/configClasses |
|
I've just noticed the default for |
| } else { | ||
| private _condition = format ["getText (_x >> 'hitpointName') == '%1'", _hitpoint]; | ||
| private _entry = configProperties [_itemInfo >> "HitpointsProtectionInfo", _condition] param [0, configNull]; | ||
| private _entry = configProperties [_itemInfo >> "HitpointsProtectionInfo", "getText (_x >> 'hitpointName') == _hitpoint"] param [0, configNull]; |
There was a problem hiding this comment.
But it's faster, so there's that!
|
If it's something where inheritance is impossible, then configClasses should be safe e.g. medical_gui |
With the latest commit I believe I have replaced all instances of |
When merged this pull request will:
configClasses.IMPORTANT
Component - Add|Fix|Improve|Change|Make|Remove {changes}.