LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView 8.0.1 loads some lvlib on startup. Why?

Hi community,
I wonder why LabView loads on startup the following project libraries:





I never used them an so I don't know how they came into some "startup-list".

Greets, Dave

Message Edited by daveTW on 06-14-2006 12:59 PM

Greets, Dave
Download All
0 Kudos
Message 1 of 7
(3,183 Views)
Does this happen when you load some vi's OR when you startup labview.

In case 1 you should look in the dependencies, and probably find you have one VI from one of these libraries (i've got the feeling not everything is put in the right place by NI...)

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 2 of 7
(3,175 Views)
Hi TonP,
I played arround a bit and found the following: when I start only LabView (via Start->Programs->...) these messages are not shown. When I start Labview by doubleclicking on a VI in my preferred Filemanager (btw. not Windows Explorer), this messages are shown, but only at the first LabView- start after booting the computer. If I then quit LabView and start it again by doubleclicking the VI, this message is not shown, possibly because parts of the LabView- Engine are still in some Windows- cache memory.
I tried then just to make a new VI by starting the naked LabView, saving the empty VI "untitled 1" without any changes (named it "test123.vi"), rebooted the computer and doubleclicked on the VI. Then these loading messages appeared again.
So do you have any ideas, why LV does this?
Greets, dave
Greets, Dave
0 Kudos
Message 3 of 7
(3,164 Views)

I believe the libraries are loading because the palettes are loading...all the screenshots of loading libraries you showed are libraries associated with VIs in the palettes.  I'm not all that familiar with the palette loading scheme, but I think I remember hearing at some point that when palettes are loaded, the libraries that own VIs in the palettes are loaded too...I think it has something to do with licensing, since your license (Base, Full, Pro) affects what VIs show up in the palettes.  And it makes sense to me that more palette loading would have to take place when double-clicking on a VI (since this action brings up LabVIEW directly in the editor), while launching from Start > Programs just brings up the Getting Started window...i.e. you're not actually editing any VIs yet.

-D

Message 4 of 7
(3,159 Views)

hi dave,

(i'm talking about LV 7.1)..

have you tried to change the options for loading control and functions palettes? (see attachment).

then i've seen you're using LV 8.0.1, i would suggest to masscompile the whole national instruments directory if you havn't done that by now (including vi.lib and instr.lib)

 

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
Message 5 of 7
(3,144 Views)
Hi Chris,
yes, I've done that already, it was that afternoon I had so much time to read the old computer magazines. I suppose you are right, it is the palette- loading thing. Thank you very much for your answer.
Greets, Dave
Greets, Dave
0 Kudos
Message 6 of 7
(3,125 Views)

you're welcome

 

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
0 Kudos
Message 7 of 7
(3,111 Views)