What does the "Copy error code files" option do in the build spec properties

[Paul_Torek]

I agree with InfiniteNothing that this would be a nice feature for applications, without needing to build an installer.  Here's my solution: in your application setup, on the Destinations category, add a new location called errors.  Specify it as <yourAppDir>\user.lib\errors.  Go to Source File Settings, highlight MyErrors.txt (or whatever) and specify location as errors.  Build.  Instruct your customers to overwrite the entire <yourAppDir> with the new one you provide, which will now include a user.lib subdirectory with a sub-subdirectory called errors, with your error file.

[InfiniteNothing]

You lost me at "instruct your customers". That's just not going to fly. It's just crazy that something on your block diagram isn't really in your code.

[Paul_Torek]

Fair enough.  My customers are all internal to my company, and engineers, so this works for me.  But I agree this isn't really good enough for prime time.

[Madottati]

"It's just crazy that something on your block diagram isn't really in your code."

Referring to this I have the question, what is the function of the error rings on the block diagrams? Is it only for readability of the block diagrams?

[JÞB]

---

@Madottati wrote:

"It's just crazy that something on your block diagram isn't really in your code."

Referring to this I have the question, what is the function of the error rings on the block diagrams? Is it only for readability of the block diagrams?

---

Yes,  the error ring populates its selections from files ending in "_errors.txt" in specific folders.

Then extends error selection with definable custom codes with format specifier support that are saved elsewhere embedded in code.

_errors.txt can't use format specifies.  The text protocol and parsing routines were define ages ago...and are really .... let's give NI something of a break and describe it as "Arthritic "

NXG will improve that according to prophecy.