|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Merging/Comparing LabVIEW VIs
We know that the professional edition of LabVIEW has diff and merge capabilities, it seems that those capabilities are not present in the FRC edition of LabVIEW. What techniques for revision control, code management, etc are teams doing?
For example, we break up our design into modules and each module has an owner. This works great for the most part but when we need to modify shared code such as telop.vi or robot globals, etc, it gets harder to keep the changes straight. Using tools such as SVN have lost much of their value since we cannot diff or merge. Thoughts? Suggestions? |
| 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 two assembly files? | Drakan290 | Inventor | 3 | 12-02-2008 15:27 |
| Merging files | fireball3004 | 3D Animation and Competition | 3 | 30-09-2007 12:18 |
| Comparing Sensor Readings in NQC | ZACH P. | Programming | 5 | 30-08-2003 17:33 |
| Spreadsheet comparing ALL First motors | Nuts4FIRST | Motors | 0 | 08-01-2002 09:20 |