View Single Post
  #9   Spotlight this post!  
Unread 14-08-2008, 08:17
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Posting LabView Code Easily?

I guess I've been on the receiving end of way too many movies watching someone write a diagram trying to demonstrate a bug. True, it has its uses, but most times, I ended up panning to the end, looking at a super grainy frame, and spotting the problem. So, the time to make the movie, time and space of the movie downloads, and time I spend watching their movie so I can make their diagram on my machine for experimenting, are all time I wish I had back.

But, the forty-seven second demo watching someone type into a text field almost convinced me I was wrong.

In other words, simplifying a VI to show the problem so that you can post a good succinct stand alone snippet of code that others can run, modify, learn from, and send back in an improved form, is my preferred way of discussing LV or C code. Screenshots are a good way to identify areas within the code and are sometimes enough. A movie has potential, but most of us don't have enough Spielberg in us to pull it off.

Greg McKaskle
Reply With Quote