05-17-2011 11:23 AM
I changed a connector pane on a commonly used vi, so I then did then find&replace trick to easily relink all 50 some instances of it. However, I was not synced to the latest versions of some files (which is not usually a problem as LabVIEW prompts you to get the latest version of the file before it checks it out). However, LV gave me a list of the 50 some files and asked if I wanted to check them out without any prompt to get latest. I clicked yes and inadvertantly overwrote the latest changes to some files.
05-17-2011 11:56 AM
Can you provide some more information so that others can try to replicate it? Such as, what kind of source code control system you were using? Was this a project that you had open?
05-17-2011 12:43 PM
The vi's did not reside in a project. Our SCC provider is perforce.
I was adding inputs and outputs to a vis conector pane that was called by numerous other vis (so they all had to be checked out when doing the relinking).
05-18-2011 07:38 PM
Thomas,
As I understand it, source control is normally linked to a project. Is this issue reproducable on your system? As I do not have perforce currently installed on my system, I cannot verify this behavior myself. Are there any other instances where LabVIEW does not alert you to an impending overwrite that you are aware of?
05-20-2011 08:49 AM
Hi, typically when we start to edit one of our vi's, LabVIEW asks if you wish to check it out. If it is not the latest version it will prompt you to get the latest version before you check the file out. We never use a project and as far as I can tell LabVIEWS SCC is not tied to projects (at least not the features we use).
So, no, there's no other instances of this behavior that I'm aware of.
05-23-2011 05:56 PM
Hi Thomas,
Just to let you know, I am trying to find someone here in applications with perforce on their PC. If I find it reproducable, then I will file a bug report with R&D. I will keep you updated here as the process develops.
05-24-2011 08:29 AM
I did an internship with NI back in 2000 and I recall that NI used perforce. I'm curious what you use nowadays as our IT guy is encouraging us to move to a different system (subversion)
05-25-2011 10:02 AM
Hi Thomas,
R&D still uses perforce, but here in Applications, we don't have much use for source control, and thus rarely use it.
05-27-2011 04:00 PM
Hi Thomas,
What version of LabVIEW and Perforce do you use?
05-31-2011 02:35 PM
LabVIEW 2010 service pack 1 32 bit, P4 Windows Client version 2007.3