hmm, it appears we may be having a newline problem in your newline solution 🙂 Lemme see if I understand what you are saying. In my version of test stand, the expression for the "Add ReportText (Outbuffer)" step is currently:
Locals.ReportText = Parameters.Result.ReportText,
FindAndReplace(Locals.ReportText, "\n", "<BR>"),
Locals.ReportEntry += "<TR><TD COLSPAN=2 BGCOLOR=" + Parameters.ReportOptions.Colors.ReportTextBg + " valign=\"top\"><FONT SIZE=-1>" + Locals.ReportText + "\n"
This is different than what you have. If I assume that the difference is because the site translated your <br>'s into linebreaks, then your propsed solution would be:
Locals.ReportText = Parameters.Result.ReportText,
FindAndReplace(Locals.
ReportText, "\\n", "<BR>"),
Locals.ReportEntry += "<TR><TD COLSPAN=2 BGCOLOR=" + Parameters.ReportOptions.Colors.ReportTextBg + " valign=\"top\"><FONT SIZE=-1>" + Locals.ReportText + "\n"
Am I correct to say that, in this case, Teststand would now convert a string with the escape code "\n", into a <br>, while leaving literal newlines and carriage returns (ASCII 0x0A and 0x0D) as they are?
Also, a side question on the binding strength of the comma operator. is the expression 'a = b , f(x)' interpreted as '(a = b) , f(x)' or 'a = (b , f(x))' ?
Oh, and yes I have been using the DLL method because it's faster. But lemme get back to you on that, because we may just end up outputting all this analyzed data I am talking about to a separate html file and just linking to it, from the TS generated html report. This would make my newline problem not a problem any more.
thank you!
jackson