Comments for Seneca5 Software Blog http://www.seneca5.com/blog Expert LabVIEW™ Development Thu, 10 Jun 2010 22:04:25 +0000 hourly 1 http://wordpress.org/?v=3.0.1 Comment on Popcorn Trivia by Justin Goeres http://www.seneca5.com/blog/2010/06/popcorn-trivia/comment-page-1/#comment-645 Justin Goeres Thu, 10 Jun 2010 22:04:25 +0000 http://www.seneca5.com/blog/?p=510#comment-645 Great picture! Pipoca para todos! Great picture! Pipoca para todos!

]]> Comment on May 2010 User Group Invite by Seneca5 Software Blog » Blog Archive » Popcorn trivia http://www.seneca5.com/blog/2010/04/may-2010-user-group-invite/comment-page-1/#comment-644 Seneca5 Software Blog » Blog Archive » Popcorn trivia Thu, 10 Jun 2010 21:04:02 +0000 http://www.seneca5.com/blog/?p=483#comment-644 [...] was some discussion during the Popcorn Tweets demonstration about where the interest in the device came from. Although people from all over the [...] [...] was some discussion during the Popcorn Tweets demonstration about where the interest in the device came from. Although people from all over the [...]

]]> Comment on May 2010 User Group Invite by JKI Software Blog · Popcorn Tweets at Raleigh Users Group, Tuesday, May 4th http://www.seneca5.com/blog/2010/04/may-2010-user-group-invite/comment-page-1/#comment-496 JKI Software Blog · Popcorn Tweets at Raleigh Users Group, Tuesday, May 4th Fri, 30 Apr 2010 20:13:07 +0000 http://www.seneca5.com/blog/?p=483#comment-496 [...] Tuesday, May 4th, I will be doing a presentation at Seneca5’s monthly user group meeting. The topic will be Popcorn Tweets: Going Viral with LabVIEW and JKI. Dave Britt (Popcorn Tweets [...] [...] Tuesday, May 4th, I will be doing a presentation at Seneca5’s monthly user group meeting. The topic will be Popcorn Tweets: Going Viral with LabVIEW and JKI. Dave Britt (Popcorn Tweets [...]

]]> Comment on Automatic, Smautomatic by Jim http://www.seneca5.com/blog/2010/03/automatic-smautomatic/comment-page-1/#comment-179 Jim Mon, 22 Mar 2010 10:50:06 +0000 http://www.seneca5.com/blog/?p=326#comment-179 Ha! I cut my teeth on LabVIEW 8.2, when I first heard of automatic tool selection I thought I'd try it. I was surprised to find that I had been using it all the time. I'd like it, too, if my workshop handed me whatever tool I needed. I've come to the conclusion that this is a classic situation of "old dog, new trick". :D Ha! I cut my teeth on LabVIEW 8.2, when I first heard of automatic tool selection I thought I’d try it. I was surprised to find that I had been using it all the time. I’d like it, too, if my workshop handed me whatever tool I needed.

I’ve come to the conclusion that this is a classic situation of “old dog, new trick”. :D

]]> Comment on Errors, Errors, Everywhere by Tim http://www.seneca5.com/blog/2009/08/errors-errors-everywhere/comment-page-1/#comment-10 Tim Wed, 05 Aug 2009 22:27:34 +0000 http://blog.seneca5.com/?p=13#comment-10 Hi Craig, I made a GOOP3 Singleton wrapper for your error logger and now it's a drop in replacement for the "Clear Errors" but it actually logs! I also used your trick of using the "Get Errors" 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's an error, and then clicking the indicator pops up the error dialog. Finally, professional quality error handling across all vi's and through all hierarchy! Of course, the problem with that is I found some errors I didn't know about and actually had to take the time to fix them :-) Thanks for sharing your error handler ... Hi Craig,

I made a GOOP3 Singleton wrapper for your error logger and now it’s a drop in replacement for the “Clear Errors” but it actually logs! I also used your trick of using the “Get Errors” 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’s an error, and then clicking the indicator pops up the error dialog.

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

Thanks for sharing your error handler …

]]>