Leaderboard

I find it hard to believe that anyone claims never to overwrite errors. I'm not sure how you detect the presence or absence of a file without trying to open it, getting error 7 and then filtering it. I suppose you could list the containing folder, but that seems a lot harder. There's nothing wrong with the former method of generating an error and then clearing it. In addition there are plenty of routines that can throw a User Cancel error as a normal part of user interaction. So maybe the clarification is that you should never overwrite an unexpected error. We have a Filter Error function that is useful. I've never figured out why this hasn't been added to vi.lib. The clear errors function clears all errors, but you should only be clearing expected ones! As far as generating errors, we have one that dumps the calling path into the error source, which I'm sure is pretty common. What it also does is that you can wire anything into it, and it uses the OpenG Lvdata tools to serialize the arbitrary data to a string, and then you can get a data dump in the error message.

Added a LabVIEW Wiki page that covers this. Anyone can edit and improve it if they desire: http://labviewwiki.org/Development_Environment_Event_Callback_VIs

I've had jobs where I've almost died from boredom... does that count?

That's slick! :thumbup: The only reference that I've found to this is an article in Google's cache from Jim Kring (kudos!) coming from the OpenG tiki (which is currently down probably due to their recent upgrade). There are a lot more of these event callback VI's listed, here's a copy out of the cache (in rtf): Download File:post-3266-1140129786.rtf