|
|
|
 The big lesson we learned ... our past does not limit our future, that superior attitude will beat out big budgets. - [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| The big lesson we learned ... our past does not limit our future, that superior attitude will beat out big budgets. - [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#4
11-02-2009, 20:16
|
|||
|
|||
|
Re: Reentrant VIs
Yep. That feature isn't fully supported in RT. A workaround would of course be to open the VI and save two versions under two names. Make them not be reentrant and now you can debug. You then of course need to be careful if you need to make edits. Once debugged, put it back to reentrant.
Greg McKaskle 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Best Practice for Posting LabView VIs? | DonRotolo | National Instruments LabVIEW and Data Acquisition | 8 | 09-04-2010 22:37 |
| Merging/Comparing LabVIEW VIs | Terry Sherman | NI LabVIEW | 7 | 30-08-2009 10:30 |
| Adding Inputs or Outputs to existsing VIs | paulcd2000 | NI LabVIEW | 7 | 12-01-2009 22:39 |
| DAQmx VIs missing | Barry Lazzer | LabView and Data Acquisition | 2 | 30-01-2007 13:06 |
Threaded Mode