Change Details

Since 1.94 (and it's hotfix) using `profileNamespace getVariable ["var", 0.5]` in `CfgUiGrids` (custom layout item) forcefully sets the grid position to 0. This is happening because 1.94 switched to `BIS_fnc_parseNumberSafe`. `profileNamespace` is not in the `"MATH_OPS"` array which checks tokens in the string, so it thinks the string is "unsafe" and returns 0.

Since 1.94 (and it's hotfix) using `profileNamespace getVariable ["var", 0.5]` in `CfgUiGrids` (custom layout item) forcefully sets the grid position to 0. This is happening because 1.94 switched to `BIS_fnc_parseNumberSafe`. `profileNamespace` and `getVariable are not in the `"MATH_OPS"` array which checks tokens in the string, so it thinks the string is "unsafe" and returns 0.

Since 1.94 (and it's hotfix) using `profileNamespace getVariable ["var", 0.5]` in `CfgUiGrids` (custom layout item) forcefully sets the grid position to 0. This is happening because 1.94 switched to `BIS_fnc_parseNumberSafe`. `profileNamespace` isand `getVariable are not in the `"MATH_OPS"` array which checks tokens in the string, so it thinks the string is "unsafe" and returns 0.