Jump to content

Allow Defined Destination of Included Dependent Code


jgcode

Recommended Posts

This is a question / feature request (depending if my thoughts are correct or not).

 

I am trying to find out the location for VIs that are included dependencies in VIPM:

 

The reason being I was seeing it get placed in weird locations - I expected it under like a main folder of the distribution not e.g. in parallel or some other location.

post-2618-0-08214100-1303780099_thumb.png

 

What I now think is, is that VIPM uses the Toolkit VIs location - is this correct?

Because I able to get it how I wanted (but I don't always use this location).

 

post-2618-0-09628500-1303780086_thumb.png

 

So I thought it may be cooler if I could define this location somehow?

I guess this one ties into this idea too.

Link to comment
Share on other sites

Correct. You don't have explicit control over this folder location.

 

The internal dependencies are always placed in a folder in parallel to the folder which is defined as the main location of your source (with a suffix _internal_deps). By default, this is the Toolkit VIs folder or it can be another custom folder you have selected for your source.

 

2011-04-26_1419.png

 

Is there a specific technical reason why you would want to control this other than for good looks?

And, do you have a suggestion on what the best way to expose this on the UI would be?

 

There is already an internal case discussing this question with possible solutions case#10912

Link to comment
Share on other sites

Correct. You don't have explicit control over this folder location.

 

The internal dependencies are always placed in a folder in parallel to the folder which is defined as the main location of your source (with a suffix _internal_deps). By default, this is the Toolkit VIs folder or it can be another custom folder you have selected for your source.

 

post-3-0-93113000-1303852913_thumb.png

 

Is there a specific technical reason why you would want to control this other than for good looks?

And, do you have a suggestion on what the best way to expose this on the UI would be?

 

There is already an internal case discussing this question with possible solutions case#10912

 

I guess I am a control freak :)

 

I am not that interested in controlling the location it was more understanding what was happening.

 

I think I was/am still missing something given your post - are you saying the folder that is set to the Project (i.e. the glyph you have highlighted in your image) is the location that the _internal_deps get stored (it just so happens that by default its Toolkit VIs so I assumed it was Toolkit VIs).

Link to comment
Share on other sites

I think I was/am still missing something given your post - are you saying the folder that is set to the Project (i.e. the glyph you have highlighted in your image) is the location that the _internal_deps get stored (it just so happens that by default its Toolkit VIs so I assumed it was Toolkit VIs).

Yes, that is correct.

 

So, a way to control the _internal_deps path would be to specify a custom Toolkit VIs path - which would define the parallel dependancies path. And then make all the other locations different - to specify your other locations (By unchecking the 'use destination of parent' checkbox)

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.