|
|
|
 A FRC team without engaged and motivated students is like a car without wheels... it isn’t going to go very far. - E. Wood [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| A FRC team without engaged and motivated students is like a car without wheels... it isn’t going to go very far. - E. Wood [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#2
09-09-2008, 10:22
|
|||
|
|||
|
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 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Posting LabView Code Easily? | Greg Marra | NI LabVIEW | 17 | 25-11-2009 16:49 |
| DAQmx VIs missing | Barry Lazzer | LabView and Data Acquisition | 2 | 30-01-2007 13:06 |
| Suggestion for posting... | Billfred | CD Forum Support | 3 | 09-01-2005 16:18 |
| Custom Dashboard code for LabVIEW ready for download. | archiver | 2001 | 3 | 24-06-2002 00:49 |
| Posting need for help. | nick reynolds | General Forum | 3 | 16-10-2001 08:05 |
Threaded Mode