Community Nugget 03/25/2007

[tst]

I'm not sure what your question is, or how it's related to this thread, but after putting something in the user.lib folder, you need to restart LabVIEW (or call the App.Refresh Palettes method) in order to see it in the palettes.

[Cory_K]

nevermind, I figured it out

[Cory_K]

Actually, I only partially figured it out.

If you look at the driver (I posted a link for it earlier in the thread) it has 3 parts:
Examples, Public, and Private

I have all 3 in the User Library part of the Palette, however only the latter 2 folders work.

All of the VIs in the Examples folder do not work.

Does anyone know of a previous thread that discussed how to install drivers/libraries in a little more detail.

If so, can you post a link to this thread. Thanks

[tst]

I only had a quick look at the driver and I can't say I'm impressed, as it does not seem to have any installation instructions. I didn't bother trying to unzip it. The public folder has a mnu file, which holds the palette information for it, so maybe you're not even supposed to place it in the user.lib folder, but just expected to point to that mnu file.

[Cory_K]

What is weird about the menu file is that when LabVIEW tries to load the palette,

it says that "LabVIEW detected a loop" and points to this menu.

To correct the issue, it then ignores the entire palette and fails to load.

Do I need the mnu file? 

[tst]

You don't need it if you place the VIs in the user.lib folder. LabVIEW displays everything in the user.lib folder in the palettes unless it starts with an underscore. The mnu file was probably used to create a palette of the examples and the public VIs and you were probably not supposed to place the folder in user.lib.

[Cory_K]

So I should just leave it in instr.lib?

[Cory_K]

Also, if I let it create it's own palette, there are about 5-10 VI's that you can use.

When I added the subpalettes (which I dont think i was supposed to do) there were dozens of VI's.

There were a few examples, then a lot in Public and a lot in Private.

Are most of those VI's used as sub-VI's that the 5-10 regular VI's call on?

I believe that is why it was causing a problem. 

[tst]

I really don't know since I didn't look at that driver at all. Whoever wrote it should have created installation instructions. If you want, you can try placing it not in user.lib and then using the palette editor to point to the mnu file, but I can't really suggest anything else.

[Cory_K]

Alright thanks