Seeking Help with Proper Library Design and Using .mnu Files in VIPM

[Achtu]

I'm currently working on building a LabVIEW library, and every time I update it, I find myself redoing the entire design process. This includes hiding VIs I don't want the user to see, adding icons, and other design tasks. This has become quite time-consuming, and I believe there must be a more efficient way to manage this.

I've read a bit about .mnu files and how they can help organize and manage the appearance of VIs in the LabVIEW palettes, but I'm not entirely sure how to use them effectively. I think using .mnu files might be the solution to my problem, but I'm stuck on how to properly implement them in my library design.

Could someone please guide me on how to create and use .mnu files to manage my library's palette structure.

Thank you in advance for your help!

[hooovahh]

VIPM has an package builder that is free, and has some really nice features. One of them is the ability to make a palette laying out items how you want.  Then installing this package will give the user the API you want them to see.  You don't need to create the MNU files your self manually, but if you do use the Palette API built into LabVIEW which lets you read and write MNU files.

[Achtu]

Thanks for your reply!
My question is more directed to my way of working. And I would appreciate it if someone could direct me because I'm just getting confused with this.
that's my process:

Initial Build (Version 1.0.0.1):

1. In the Build Information panel, I select the Source Directory.
2. In the Palette Tab, I design the icons for the Functions Palette.
3. I click the "Build Package" button, and after a moment, a VIP file with version 1.0.0.1 is generated from the VIPB file.

Now, after a few days, I want to release version 1.0.0.2. Here are the steps I follow:

Updating to Version 1.0.0.2:

1. In the Build Information panel, I select the Source Directory.
2. In the Palette Tab, I design the icons for the Functions Palette.
3. I click the "Build Package" button, and after a moment, a VIP file with version 1.0.0.2 is generated from the VIPB file.

Do I need to repeat these three steps every time, or is there a way to skip step 2? I’m sure there’s a more efficient approach, especially when dealing with large packages.

[hooovahh]

24 minutes ago, Achtu said:

Now, after a few days, I want to release version 1.0.0.2. Here are the steps I follow:

Updating to Version 1.0.0.2:

1. In the Build Information panel, I select the Source Directory.
2. In the Palette Tab, I design the icons for the Functions Palette.
3. I click the "Build Package" button, and after a moment, a VIP file with version 1.0.0.2 is generated from the VIPB file.

Do I need to repeat these three steps every time, or is there a way to skip step 2? I’m sure there’s a more efficient approach, especially when dealing with large packages.

Why would you repeat steps 1 and 2 every time?  Just open the the VIPB you made from the last build you made, then click Build Package.  The Palette you made previously will only have items removed if the file it references no longer exists.  You may also want to update the Release Notes or Change Log with every release but realistically that's all you should have to do.  Is your Source Directory and palette getting wiped away after each build?

[Achtu]

The VIPB is connected to a Source Directory that has 5 VIs.

Once I add another VI to the Directory, I don't see it in the Functions Palette on the Palette Tab.

How do I "refresh" the VIPB file? My refresh was done by step 1.

Importantly, I see the additional VI in the Source File Setting Tab after I click "Reset to Default" but in the Functions Palette it does not appear.

[hooovahh]

15 minutes ago, Achtu said:

The VIPB is connected to a Source Directory that has 5 VIs.

Once I add another VI to the Directory, I don't see it in the Functions Palette on the Palette Tab.

That's because you didn't add it.  The Palette does not show all VIs. It is a place where you can add your VIs, or directories that you want it to show.

If you added a VI, and the package builder already has it open, then click File >> Close, then pick your project in the new window.  Then go to Palette, then Right Click >> Insert >> Control or VI and pick your new VI.  This video shows some of the process even if it is older. 

 

[Achtu]

I completely understand! I anticipated it would work a certain way, but it turned out to function differently.

Just to make sure, if you have a VI in the Functions Pallete and you changed its Icon. You go to Palette then Right Click on the VI >> Delete and Shift. After that, Right Click >> Insert >> Control or VI.

[hooovahh]

You shouldn't need to delete and reinsert for the icon to be updated. Just close and reopen the builder if it is open to have it refresh.