LabVIEW
all labview Vi's load from different directory
OK this may be a stupid question but I done a save with options/ include VI.llbs. on my machine and now when I create a new vi whenever I try to put something on the block diagram it tells me that it is loading the files from the library that i saved for distribution. It only does this when I have the top level vi open of the library and try to open a new blank vi. It even does it when I open labview then open a blank vi and put anything down on the diagram and it does not give me this. then I can open up the top level vi from the library in question and put the same thing on the diagram and it will give me the warning. Maybe this is normal behavior, I don't know.
It just seams kind of funny that it would try to lo
ad NI VI's from the llb instead of mine. Hope some can shed some light on this. I do not want to mess anything up.
thanks in advance.
Joe
It just seams kind of funny that it would try to lo
ad NI VI's from the llb instead of mine. Hope some can shed some light on this. I do not want to mess anything up.
thanks in advance.
Joe
If I understand what you are saying, this is annoying, but normal behavior.
LabVIEW can only have one VI of a specific name in memory at a time. So if you have the top level VI in question open, all of it's sub-vis get loaded into memory. So then if you create a new VI and drop the 'General Error Handler.vi' from the palette, it will use the one already in memory from your library.
Creating a new VI right after you start LabVIEW will let you use the vi.lib files, but then when you open your application from the library, it must use any vi.lib files that are in memory first.
Usually it's best not to save a .llb with the vi.lib files unless it's required for source code control. Then it's a good idea to use the Development Environment Applicaiton
Builder from OpenG to build the library for you. This will add a suffix you specify to every VI in the library and relink them to their callers. This way, other VIs you open will use the vi.lib files.
Ed
LabVIEW can only have one VI of a specific name in memory at a time. So if you have the top level VI in question open, all of it's sub-vis get loaded into memory. So then if you create a new VI and drop the 'General Error Handler.vi' from the palette, it will use the one already in memory from your library.
Creating a new VI right after you start LabVIEW will let you use the vi.lib files, but then when you open your application from the library, it must use any vi.lib files that are in memory first.
Usually it's best not to save a .llb with the vi.lib files unless it's required for source code control. Then it's a good idea to use the Development Environment Applicaiton
Builder from OpenG to build the library for you. This will add a suffix you specify to every VI in the library and relink them to their callers. This way, other VIs you open will use the vi.lib files.
Ed
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Thanks for the quick answer Ed. This is annoying but as long as it is normal than that is OK. I have the openG tools but have never used the vi's for the development, I think I will give them a try.
Having to much fun with labview.
I love this stuff
Joe
Having to much fun with labview.
I love this stuff
Joe
