How to Retain Icon Edits Between VIPM Package Builds

[maxnoder1995]

Hello, I have a question regarding VIPM that I'm having trouble with. When I build a project, I select the root folder, edit the icons for each folder, and perform the build. This results in version 1.0.0.1.

However, when I add a new VI and want to move to version 1.0.0.2, I once again select the root folder with the added VI. But this time, I have to edit all the icons again, as they are not saved. I would appreciate any advice on how to work more efficiently with building packages and maintaining these settings.

[crossrulz]

Are you not saving a vipb file?  The vipb file remembers all of the settings for building your package, including the icons, target directory, etc.

[maxnoder1995]

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.

When I build a VIPB file using VIPM, the output is a VIP file (version 1.0.0.1). I want to add another VI and update the version to 1.0.0.2 while retaining all settings, including the icons.

Currently, I have to reconfigure the "Source Directory" each time. Although the new VI appears in the palette, I need to manually reapply all the icons, which is time-consuming.

How can I streamline this process?

[billko]

---

@maxnoder1995 wrote:

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.

When I build a VIPB file using VIPM, the output is a VIP file (version 1.0.0.1). I want to add another VI and update the version to 1.0.0.2 while retaining all settings, including the icons.

Currently, I have to reconfigure the "Source Directory" each time. Although the new VI appears in the palette, I need to manually reapply all the icons, which is time-consuming.

How can I streamline this process?

---

Something is not working right.  There is no "streamlining" because something is broken.  Unfortunately I have no idea what.  Maybe you don't have write permissions to the folder where the project is?

[tst]

---

@maxnoder1995 wrote:

When I build a VIPB file using VIPM, the output is a VIP file (version 1.0.0.1).

---

Like the others said, other than building the package (the play button), VIPB also has a save option which saves the configuration for the package, which includes all of the relevant data.

[maxnoder1995]

Thanks for your reply! To clarify, I have version 1 of my package. I want to understand the efficiently way to add a VI and upgrade the version. That's the main challenge I'm facing. I would love a breakdown of exactly which buttons to press, because I’m struggling with this section.

as much as I understood (and for sure I didn't), I need to add to my Source Directory some .mnu files.

[billko]

---

@maxnoder1995 wrote:

Thanks for your reply! To clarify, I have version 1 of my package. I want to understand the efficiently way to add a VI and upgrade the version. That's the main challenge I'm facing. I would love a breakdown of exactly which buttons to press, because I’m struggling with this section.

as much as I understood (and for sure I didn't), I need to add to my Source Directory some .mnu files.

---

That's totally confusing because part of the allure of VIPM is that you don't need to create the .mnu items.  There is an "editor" that lets you visually arrange the VIs as you want them to appear and then VIPM creates them for you.  (Actually I don't even know if they are created until you build the package.)

[maxnoder1995]

It seems I'm not explaining my issue clearly, so let me walk through the process step by step:

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.

Am I missing something? Do I need to repeat these three steps each time, or is there a way to skip step 2? It feels repetitive, and I don’t see why it should be necessary to perform it repeatedly. Especially in large packages.

[raphschru]

---

@maxnoder1995 wrote:

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.

---

Simply don't reselect the Source Directory each time, for some reason it overwrites your custom palette and regenerates a default one.

It may be a bug or not, but normally this folder has no reason to change at each update.

If you want to refresh the content of the Package Source Folder in the Source File Settings, just press the Refresh button:

Regards,

Raphaël.