Temporary file problems when using source control

[alecjcook]

Hi,

   When using LabVIEW's SCC to check out source code (I am using Perforce) the Perforce command line client will create a copy of the file I want to check out in a temporary directory... This upsets LabVIEW because it then doesn't know which vi to use, as there are now duplicate copies on my HD. Does anyone know how I can stop the Perforce Command Line Client that is embedded in LabVIEW doing this?

Many thanks, Alec

[Liam_A]

Hi Alec,

Thanks for your forum post.

Perforce is a third party peice of software that we can integrate with from within the LabVIEW project.

The website for Perforce can be found here.

In terms of what is occuring by when loading files, what naming conventions are you using and whereabouts are the SCC files being stored?

Look forward to hearing from you,

Liam

[alecjcook]

Hi Liam,

   The source code is stored in a unique directory on my HD, the paths are all correct for LabVIEW. when I use perforce, I had disabled the checkbox saying "create temorary read only files" in the preferences. But LabVIEW talks to perforce via P4CMD, and this setting is not available, hence a read only file is created in c:/users/temp/ReadOnly_Whatever.vi

Cheers, Alec