LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to configure VI browser plugin

I have several VI libraires (llb files) that contain 100+ sub vi's.  I have them stored on a server that I access remotly. 
When I attempt to access a llb file on the network the NI browser plugin on my local machine insists on opening the llb file in "view icon" mode.  The browser plugin completly ignores the fact that I have explorer set to "view details" not icons. 
This would only be a minor issue except for the fact that viewing a large llb file in icon mode over the network can lock up my computer for 5-10 min. 
The question is then, is there a way to configure the browser plugin?  Registry tweek, ini file tweek,  etc???
 
0 Kudos
Message 1 of 4
(3,241 Views)

Hi BDS,

I am sorry that this thread was not answered sooner.

By "NI browser plugin", do you mean the VI Library Manager ? I am having trouble reproducing the problem...can you please provide more details.

Regards,

Ankita 

0 Kudos
Message 2 of 4
(3,222 Views)
This will not be an issue if you are connected by a fast network with no congestion.  Part of my problem is that I am located at a large corporate facility.  The actual access speed through my network can be very slow at times.  I am not sure how you could exactly duplicate my problem. 
Do you mean that when you open a .llb file in explorer that it always opens in "details" view?  On my computers, no matter how many times I access a .llb file I always get the icon view.  My work around is to just copy the .llb file onto my local hard drive and then open it from there.  Otherwise  I can use Labview to open the .llb file.  This works fine as well.  I Just have to remember not to click on a .llb file (that is stored remotely) from within explorer.
0 Kudos
Message 3 of 4
(3,218 Views)

You are right....I tried to change my internet explorer folder settings to "details" view but whenever I open a .llb, it gets opened in icons view. I have made a product suggestion for this feature. Meanwhile a workaround would be to use LabVIEW's library manager to open the file.

Regards,

Ankita

 

0 Kudos
Message 4 of 4
(3,209 Views)