04-29-2006 12:05 PM
05-04-2006 08:04 AM
07-21-2006 12:31 AM
I'm a bit late, but I also want to give my comment.
Basically I don't use the revision history. If a major SW modification is done and I later want to know what changed, I had to open the revision history of each vi. I think that's kind of annoying.
I use MS visual source safe and usually a separe document describing the changes. Doing it this way, I have one document where all changes are included and see where they were made.
What I wish for future versions of LV, is the possibility to have different SCC projects accessible. Now in LV8.0 I gave it another try (I first did in LV6.1 but for me it did not work) and had to discover, that I just can connect to one project in the SCC - and this was accessed from each LV project. Definitely not what I want. If each LV project could be mapped to a SCC project it would be quite nice. Then I would not have to open SCC all the time but could manage it directly from within LV.
07-26-2006 04:05 PM
I typically use the revision history by setting up Tools-->Options to "prompt on save."
When changes are minor (change names of controls/indicators, add comments, edit icon, fix aesthetics) I don't add to the Rev history. When changes are more significant, I usually will.
As for usefulness, it has been a really big help only a few times and has been a little bit of help many more times. I'm not certain if the sum total of the time I've put into the Rev history comments has paid back or not. The time cost is generally about a minute or less but occurs frequently. The time savings are generally many minutes or hours but they occur much less often.
I'd prefer to keep this feature around - it's already off by default for those who don't care to use it.
07-27-2006 07:46 AM
Do you use source code control when working with your files? The impression I get is that people use VI History as you do - a quick way to track minor changes. In theory, if you use source code control, those same notes would be included in comments when you check in the file with your changes.
07-27-2006 09:59 AM
08-09-2006 08:37 AM
Well, I'm late as usual (I had never even looked at this forum until today), but figured I'd add my comments.
I've always tried to use VI History to add meaningful comments and I keep the 'prompt when changed' setting on. I also use SCC (VSS), but I wouldn't want native VI History to go away. As other posters have described, I may check a VI out of VSS, change/save it multiple times, then finally check it back in. It would be a nice feature of the SCC tools if they could get the VI->HistorySince(LastCheckedInDate), and pre-fill the SCC checkin comment, so you could use the VI's recent history changes as a starting point. In fact, there is/was a VI Server property with exactly that name (HistorySince), which IIRC took a U32 timestamp as an argument, though I think it's a private scripting property. At any rate, it seemed like it should be useful in the SCC tools - don't know why it wasn't used.
I have also taken to the practice of putting SCC tags into the VI description which get updated by the SCC tools. Of course, they're of the fixed-length type (double-colon), for example:
$Revision:: 5 $
$Modtime:: 02-09-23 11:40 $
$Author:: Dboyd $
This way, I can idle the cursor over VIs in the hierarchy tree, and see the relevant SCC info. I hope this doesn't give future LV versions fits if it messes up some internal CRC/signature checking, but it's worked well for several years now.
Hope this is useful info.
12-18-2006 04:37 AM
04-26-2007 03:59 PM
07-04-2007 11:41 AM