<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Errors, Errors, Everywhere</title>
	<atom:link href="http://www.seneca5.com/blog/2009/08/errors-errors-everywhere/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seneca5.com/blog/2009/08/errors-errors-everywhere/</link>
	<description>Expert LabVIEW™ Development</description>
	<lastBuildDate>Thu, 10 Jun 2010 22:04:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Tim</title>
		<link>http://www.seneca5.com/blog/2009/08/errors-errors-everywhere/comment-page-1/#comment-10</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 05 Aug 2009 22:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seneca5.com/?p=13#comment-10</guid>
		<description>Hi Craig,

I made a GOOP3 Singleton wrapper for your error logger and now it&#039;s a drop in replacement for the &quot;Clear Errors&quot; but it actually logs!  I also used your trick of using the &quot;Get Errors&quot; in the Event Timeout case where it updates an error indicator on the front panel and this is also a great place for sending the error to an error handler. I liked your idea of making it invisible if there are no errors but then showing it if there&#039;s an error, and then clicking the indicator pops up the error dialog. 

Finally, professional quality error handling across all vi&#039;s and through all hierarchy!  Of course, the problem with that is I found some errors I didn&#039;t know about and actually had to take the time to fix them :-)

Thanks for sharing your error handler ...</description>
		<content:encoded><![CDATA[<p>Hi Craig,</p>
<p>I made a GOOP3 Singleton wrapper for your error logger and now it&#8217;s a drop in replacement for the &#8220;Clear Errors&#8221; but it actually logs!  I also used your trick of using the &#8220;Get Errors&#8221; in the Event Timeout case where it updates an error indicator on the front panel and this is also a great place for sending the error to an error handler. I liked your idea of making it invisible if there are no errors but then showing it if there&#8217;s an error, and then clicking the indicator pops up the error dialog. </p>
<p>Finally, professional quality error handling across all vi&#8217;s and through all hierarchy!  Of course, the problem with that is I found some errors I didn&#8217;t know about and actually had to take the time to fix them <img src='http://www.seneca5.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Thanks for sharing your error handler &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
