I have observed some unusual behavior with the "Search/Split String Function", and would love some help to learn why and/or how to work-around this issue.
Behavior:
1. When the "Search/Split String Function" is given a 'newline' (\n) delimited string constant, it is able to correctly parse and return the first token before the newline delimiter.
2. However, when the "Search/Split String Function" is given the exact-same 'newline' delimited string through a 'string control' (i.e. a string input text field), it is incapable of finding any 'newline' delimiters.
I have attached a minimal example from Lab View 2018 patch 2 (18f2) that demonstrates the issue.
Question 1: Does anyone know what's going on? Is this a bug, or am I missing something obvious, like some function parameter or string-encoding?
Question 2 (which is less important): I would ultimately like to use the "Search/Split String Function" to split on a null character ('\0'). I know some other LabView string functions do NOT work with the null character. Does anyone know if this "Split String Function" works on null characters?
- Thanks!