LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
keithn

Addition to error message information

Status: Declined

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.

I would find it real useful to know the time an error code is generated. If "time" were to be grouped into the current standard bundle of "status", "code" and "source" that would be just super.

13 Comments
SteenSchmidt
Trusted Enthusiast

@AQ: Since some change is necessary to include such timestamps in some way, I merely suggested a simple way to get them into the existing error wire. I don't see any difference between offering a subVI to add the timestamp and making some heavy change with a class instead of the current error cluster. Granted, the change has to be made by the programmer of the error generator, but that point is moot in this case - any change to the error generator has to be made by that programmer. My suggested change is simpler - install the GPower Error & Warning toolset and that programmer could have a drop-in VI that adds the timestamps for her.

 

I'm not pushing my toolset, I'm just offering a solution now instead of folding your hands behind your neck for the next 5 years waiting for something native to magically show up in LabVIEW core. The current error cluster with all its nooks and crannies is a beast to master. That's the reason I did that toolset, because it was near impossibly to implement perfect error handling in an application without it. It was always something like, "Hmm, we know we should be adding a description label here, but it's such a hassle", or "Here we really could use a global error description since we throw this error alot, but we also need to be able to change that description on certain occasions, and we can't do that", or "The correct format of the blame call chain within the source string is...oh, bugger, I can't remember", or "I need to keep both of these errors, but I can't spare the time to replace the error cluster with an array of error clusters in all my code" etc.

 

Cheers,

Steen

CLA, CTA, CLED & LabVIEW Champion
AristosQueue (NI)
NI Employee (retired)

I was reading your post as suggesting a full workaround for the idea and just trying to make sure we didn't overstate the case. As a helper, it's great.

Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.