LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
LV_Warrior

Save as function default directory with autopopulating folder.

Status: Declined
Issue is not reproducible

Using autopopulating folders next to the project file inside a mother directory has the great advantage that the whole directory can be copied and renamed without raising any conflicts.

That way it is easy to keep versions apart and independant of both the other versions and the PC it is located on.

After opening the projectfile, saving any VI will default to the directory next to the others inside autopopulating folder within the mother directory.

BUT NOT SO if you are trying to save a CTL file. In that case the default directory is still the old directory name that belongs to the previous version of the mother directory before that directory was copied.

The project file apparently is still working with an absolute path for that particular file type.

 

This is something that can probably be fixed relatively easy ?

7 Comments
AristosQueue (NI)
NI Employee (retired)

Can you give a very explicit (i.e. use fake directory names) step-by-step description of the issue? I couldn't reproduce what you're describing, but I'm not sure I'm copying files correctly from your write up.

AristosQueue (NI)
NI Employee (retired)

Video recording would also be fine if you have an easy way to record and post. Some customers use Jing for such.

LV_Warrior
Member

The structure I have looks like this:

 

**************************************************

MotherDirectory_00

     -AutopopulatingFolder_1

          - VI_1

          -VI_2

          - CTL_Folder

               -CTL_File_1

               -CTL_File_2

   -AutopopulatingFolder_2

   - Project.alsiase

   - Project.lvlps

   - Project file

******************************************************

I copy -in windows- I copy the whole MotherDirectory_00 to MotherDirectory_01.

Then I start the project file in MotherDirectory_01 without LV complaining about other VI copies with the same name somewhere in my PC.

Working from the project explorer I can copy VI_1 while LV will for the new VI automatically suggest a location next to the original in MotherDirectory_01/AutopopulatingFolder_1

However, if I create a new typedef and want to store corresponding CTL_File_3, then LV suggests a location inside the old mother directory MotherDirectory_00

As filepaths are extremely long it needs a keen eye and alertness to not let this happen. If it does, the trick of copying the whole project with just one independant directory will fail.

 

Best regards, Paul

 

NateBraska
Member

Hi Paul,

 

This is possibly a bug if there is an inconsisitency between the file types. In that case, I can create a Corrective Action Request (CAR) to track the problem for NI R&D.

 

Before jumping into that, I am interested in what menu or method you are using the copy the VI and create the new typedef. From my tests:

  • If you open VI_1 and select File > Save As...> Copy (any version of copy), then it suggests the same location as VI_1.
  • If you right-click in the project on Folder1 and select New > VI (or Control), then it suggests Folder1 as the location.
  • If you select File > New VI from the project or a VI, then it suggests a folder location where you most recently saved a file in LabVIEW; this could be from the previous MotherDirectory.

Is that last bullet point the issue you are seeing? The other two seem to suggest a location that is updated to the new MotherDirectory location.

 

Best Regards,

 

Nathan Burke

Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect

LV_Warrior
Member

Indeed, as in the last bullet, It is probably the last used file location which is within MotherDirectory_00

I am not talking about copying VI's, It happened while updating  type defs.

The good news however Nathan is: Whatever I do, I now cannot reproduce the problem myself.

I guess for now we consider this problem solved ?

AristosQueue (NI)
NI Employee (retired)

LV_Warrior: Keep your eyes open for it happening again and let us know. We can close the idea now and reopen it if you get steps to reproduce. If it turns out to be a bug, we'll file it appropriately. Thanks for the feedback.

Darren
Proven Zealot
Status changed to: Declined
Issue is not reproducible