Greycat and rbergers,
I took a look at the SearchandReplaceOdd.vi and I’ve got an update for you on the issue. I was able to reproduce the issue from scratch, and this is definitely unexpected behavior that R&D will have to examine and fix for a future release. I’ve also got a few things for you both to look at in your own code to work around this behavior in the future:
1) the ’\’ Codes Display option must selected for the search string constant in order to observe this behavior (right click the constant)
2) when there is an indicator on the output of the Search and Replace String VI, the behavior cannot be seen
3) when the input to the Search String input is a control, the behavior cannot be seen
4) the behavior is not limited to the \s Search String; the behavior can be seen when using the \t, \n, etc
5) when the input to the Search String input is not found in the Input String, the behavior cannot be seen
The code I have attached is a summation of some of the testing I have done. I have not tried rbergers’ code in this new light, but I can imagine that #1 above is why Jarrod S. was not able to reproduce the behavior from scratch. You may be able to experiment a little more with this VI to determine a set of criteria for reproduction. Either way, the corrective action will cause a reexamination of the Search and Replace String VI and its functionality. This strange behavior should be corrected in a future release. Thank you both for helping us to identify this strange behavior and I hope the above criteria can help you avoid these strange effects.
