Great, and thanks for posting back! So the issue was not exactly
with E-Prime Task Events, but with including control characters in
the output string.
Hmm, then you should still be able to get it to work with Task Events
by defining your string plus carriage return/newline into an
attribute, and then using the attribute reference in Task
Events. E.g., with inline code (could do this once at the Sesson level),
c.SetAttrib RunString, "RUN" & ebCrLf
and then for "Custom" in Task Events use
[RunString]
Even better, just try either of the following strings for Custom in
Task Events:
RUN\n
RUN\r\n
The generated code shows that it properly includes the escaped
control characters (\n, or \r\n), so this should work, but I need
someone else to run this and confirm.
So the lesson here seems to be that we have to know how to embed
standard escaped control characters in our Custom strings for Task Events.
Twitter: @EPrimeMaster (
https://twitter.com/EPrimeMaster)