View Single Post
  #2   Spotlight this post!  
Unread 09-09-2008, 10:22
Greg McKaskle Greg McKaskle is online now
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: Best Practice for Posting LabView VIs?

Personally, I think a description of the code, commonly with an image is a good approach. If you want people to run it, then attach the VI. The VI may have dependencies, but often those are easy to stub out to focus on the question or issue. And in fact, that stubbing and prepping the code to submit will often add insight as to what the issue was in the first place and avoid the dreaded doh posts.

I haven't had good experiences with movies of VIs. Maybe that will change.

Greg McKaskle
Reply With Quote