Wow, you NI guys really got me this time. When Unflatten from String fails the 'rest of the binary string' output contains some random value from a previous execution. What a major PITA that was to sort out, random old values being recycled intermittently. Easy to reproduce in LV12 SP1
Start with a very simple VI:
Input a long enough string to get an I32 out (strings are set to hex display)
Nice and happy. Now empty the input string are run again.
Say what? Given the dearth of documentation on the expected output, it is fair to ask what it should be. Error out and the value (default of 0) are both fine, but what about the remainder string?
Input string unchanged? I say yes with a capital 'yes'.
Empty string? I could at least entertain an argument for returning the default value of the string type. A weak argument, nonetheless.
Whatever the value of the remainder happened to be last time there was a successful conversion? No way.
And no amount of Always Copy is going to help in this case.