Declining this idea for the following reasons: This would introduce state into a VI used ubiquitously across applications, including VIs running as part of LabVIEW's editor itself. It would make a global variable a standard for LabVIEW programming. And it would turn a fairly light weight VI into one that has the overhead of an array copy on every invocation.
This proposed new VI would expand upon the Clear Errors VI, and keep a history of the error codes that have been cleared. Ideally, it would have a History Length input (not shown) that, when not wired, would default to 1024 errors.
I thought of that, in fact had that drawn up at first but changed it. I'd be fine with either. If I have the code I can look it up. The error cluster has the boolean which would be redundant - they are ALL errors.
Declining this idea for the following reasons: This would introduce state into a VI used ubiquitously across applications, including VIs running as part of LabVIEW's editor itself. It would make a global variable a standard for LabVIEW programming. And it would turn a fairly light weight VI into one that has the overhead of an array copy on every invocation.
"It would make a global variable a standard for LabVIEW programming."
Wouldn't it use an action engine instead? Either way, I like the Idea and I'm going to make one for myself. It will make logging errors much much easier.
Alright, here's what I've come up with. Feel free to use it. As you can tell by the timestamp of my previous post, I didn't spend much time on it, so it might not be ideal. Seems to be working OK though.
Clear Errors with History.vi
Clears any error entered into Error In while recording the timestamp and errors (not warnings) that enter the node. Reset will clear the list of errors and will also update the History Length.
Although it was declined I just saw this idea and gave it kudos. I think it was improperly declined because Broken Arrow was not suggesting modifying the existing Clear Errors but adding a new one.
