how to prevent vis consisting of a lot of subvis

[Mark_Yedinak]

Besides working with projects which you defintiely should be doing you really could benefit from using source code control. It will really making working on multiple machines much easier. Subversion (SVN) is pretty easy to setup and use.

Depending on the nature of your code you may also want to use a library (lvlib) instead of a project. Libraries are good for collections of VIs that are reused in multiple projects. Do try to organize your libraries so they make sense though. Don't mix a bunch of string handling stuff with a bunch of math related VIs in one library for example.

[Mark_Yedinak]

---

@Prabhakant Patil wrote:

You can use state machine architecture or any suitable architecture, which will help you to aviode this

---

You know, I don't normally do this type of thing but can you please try to post meaningful and related information. Your reply has nothing to do with this topic. You have been doing this in multiple threads and it is more of a distraction than a help.

[newbieeng]

hi again,

I succeeded in preparing a labview project, but I experienced that it only contains paths instead of subvis. Is there a way to constitute one file that includes all subvis, texts, etc. used by the main vi? Or is there a configuration on labview project that I can do it manually?

[Yamaeda]

In the project, you'll have to create a source code distribution. This'll export all used code to a specific place, which can then be zipped in normal manner. You could go with a LLB, but it's usually not recommended nowadays.

/Y 

[newbieeng]

---

@Yamaeda wrote:

In the project, you'll have to create a source code distribution. This'll export all used code to a specific place, which can then be zipped in normal manner. You could go with a LLB, but it's usually not recommended nowadays.

/Y 

---

you said "You could go with a LLB, but it's usually not recommended nowadays.". what did you mean? I reaaly confused.

[altenbach]

---

newbieeng wrote:

you said "You could go with a LLB, but it's usually not recommended nowadays.". what did you mean? I reaaly confused.

---

What is your question? Do you want to know what a llb is or do you want to know why it is not recommended?

An llb is a very old container for VIs. It was useful in the old days (before windows 95) to e.g. support long names for VIs, back in the days when filenames were limited to 8+3 characters by the OS. LLB's are somewhat fragile and should not be used as a primary container for your development. If it gets corrupted in some way, you might lose all your VIs in it.

You can use the llb manager to convert folders to llb's and vice versa. I recommend to use regular folders to organize the VIs of your project.

[newbieeng]

---

@altenbach wrote:

---

newbieeng wrote:

you said "You could go with a LLB, but it's usually not recommended nowadays.". what did you mean? I reaaly confused.

---

What is your question? Do you want to know what a llb is or do you want to know why it is not recommended?

An llb is a very old container for VIs. It was useful in the old days (before windows 95) to e.g. support long names for VIs, back in the days when filenames were limited to 8+3 characters by the OS. LLB's are somewhat fragile and should not be used as a primary container for your development. If it gets corrupted in some way, you might lose all your VIs in it.

You can use the llb manager to convert folders to llb's and vice versa. I recommend to use regular folders to organize the VIs of your project.

---

I just asked to Yamaeda what he meant with "You could go with a LLB, but it's usually not recommended nowadays.". Just it.

[Yamaeda]

Altenbach said it well, a LLB is basically a zip file you can work directly to/from. As such, it's easy to move and distribute and fragile if something happens.

/Y 

[newbieeng]

---

@Yamaeda wrote:

Altenbach said it well, a LLB is basically a zip file you can work directly to/from. As such, it's easy to move and distribute and fragile if something happens.

/Y 

---

Ok, I got it. Thank you. I created a LLB container. I recognized that in the LLB manager window I cannot see any text files but when I run the main VI it works. Do you know whether LLB contains text files in it or not?

[altenbach]

LLB's can only contain classic LabVIEW related files (vi, vit, ctl, ...).

So why exactly are you still insisting on using llb's? Makes no sense to me. 😮