Duplicate hierarchy not working or brain not working?

[pallen]

Greetings folks,

I'm having a tough morning it seems.  Besides the crashing, I can't seem to remember how to save VI and all of it's subVIs to a single location. 

I've done this many, many times in previous versions of LV and never had a problem.  But 8.5.1 has stumped me.

When I try to save my VI, I'm clicking "Save As".  I select "Duplicate hierarchy to a new location"   I click continue. 

I am prompted to name the file.  I type "Test".   Then I click "Save". 

I'm expecting this to either save all the VIs in a folder called test, or something similar to that. 

It's not.

What it's doing is creating a folder called "Test" and creating two more folders inside that one.  One folder is the name of the root folder of the project I'm working on.  The other is the root folder of the project I originally cut and pasted a piece of code from.  Inside that folder is the entire original project I snipped the little piece from. 

Why is that there? 

I've tried saving the little snippet of code as it's own seperate VI, and then trying again. 

Same thing.

I've shutdown LabVIEW completely and tried again; this time never opening anything else.  Again I end up with the entire project and this weird folder thing. 

The subVIs I want to copy into a new location are located inside an .llb (The old project)  Is this why I keep ending up with the whole thing?  Is there any way to just get the SubVIs that are in my little snippet of code without having to copy them manually? 

Thanks. 

[altenbach]

I usually make a project and  just built a "Source Distribution". Do you have the application builder?

[Christina_R]

Hi Patrick,

What you're describing sounds very odd (and it's possibly a bug).

The way Save As>>Duplicate Hierarchy works is that it copies the entire hierarchy to the folder you specify. We preserve folder hierarchy (rather than converting to a flat folder) so that it works even if you have duplicate names (e.g. if you have multiple libraries or classes with the same VI name).

So, if your duplicate hierarchy is picking up your original project, that would imply that your "snippet of code" still depends on those files for some reason.

Source distributions give you more control over the copy, and will probably work for you. But I wonder if you have something cross-linked, if the Save As>>Duplicate Hierarchy copy contains items you don't expect to be there.

- Christina


Message Edited by Christina R on 05-22-2008 03:15 PM

[pallen]

Hi Christina,

Thanks for your reply.

After thinking about it a little more, I'll guess that I was ending up with the entire .llb of the code I was snipping from because the utility wasn't able to pull the individual VIs out of a .llb file.  So it just put the whole .llb file in a folder. 

Technically everything would still work.  The SubVI I wanted was inside that .llb   I just didn't want/need the whole thing. 

I ended up just pulling the SubVIs I needed out of the .llb manually.  But I think I'll try and duplicate this later and see if I'm correct in my assumption. 

[pallen]

Hi Altenbach,

Thanks for your reply.

I do have the Application Builder.  Although admittedly I've used it only once since upgrading to LabVIEW 8.5  So I wasn't aware that creating a source distribution is now handled through it now.  I was used to the "Save with Options" dialog from previous versions.

I'll have to check that out, as I used to archive all my projects as source distros.