-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CBA_Settings_fnc_parse fails to parse strings over multiple lines #1573
Comments
Why do you think it ougth to in the first place?
This syntax seems wrong. What are those semi-colons doing in there? |
I'm not sure where you got your syntax, but that's not the syntax I wrote. This is what I posted earlier: force tsp_cba_breach_military = "[
""Land_Budova4_in"",
""Land_Budova4""
]"; There are no semicolons in between, there is only one at the end. The following code is only a partial result within "force tsp_cba_breach_military = ""[;
""""Land_Budova4_in"""",;
""""Land_Budova4"""";
]"";
" However, this partial result shows why the parsing of that setting fails: It think it's multiple settings, despite it only being one. |
Ok. It doesn't support multiline and was never intended to. |
Thanks for the answer. Can this information be mentioned on the wiki page? |
I can't edit the page, unfortunately. |
Added info to the Wiki: |
Mods (complete and add to the following information):
2.12 profiling branch
3.15.8 steam release
Description:
If you use a
cba_settings.sqf
file with a setting value of a string spread over multiple lines, it will not parse the setting correctly.Steps to reproduce:
cba_settings.sqf
file within the mission folder.cba_settings.sqf
file:CBA_Settings_fnc_parse)
:Result:
This leads to
CBA_settings_fnc_parse
to fail parsing this setting.Expected behavior:
Result should be:
"force tsp_cba_breach_military = ""[""""Land_Budova4_in"""",""""Land_Budova4""""]"";
Where did the issue occur?
Log Files:
Additional context:
The solutions I can come up with:
CBA_Settings_fnc_parse
.Screenshots:
I can add some if necessary.
The text was updated successfully, but these errors were encountered: