Palette .mnu files installed to <vi.lib> instead of <menus>/Categories

[AMP]

I am using the free version of VIPM 2013.0.0 (Bulid 1878). When I make my own custom package using the package builder, the spec file that is generated is placing the palette menu items in <vi.lib>, instead of <menus>/Catagories:

 

[File Group 1]
Target Dir="<vi.lib>/MEI/Type Helpers"
Replace Mode="Always"
Num Files=1
File 0="functions_mei_lib_binary_string_helper.mnu"

[File Group 2]
Target Dir="<vi.lib>/MEI/Type Helpers"
Replace Mode="If Newer"
Num Files=1
File 0="dir.mnu"

 

When I install the package in LabVIEW 2010, I can see my palette on the function palette. However, when I install on LabVIEW 2012, I see nothing on the function palette. If I copy the menu items from <vi.lib> to <menus>/Catagories, then I can see this in LabVIEW 2012. For some reason, LV2010 is way more tolerant with dodgy menu installs than 2012 is.

 

Here is what my palette set looks like in my package's .vpib file:

 

    <Palette_Sets>
     <Palette_Set_Name>MEI</Palette_Set_Name>
     <Use_Custom_Category>true</Use_Custom_Category>
     <Custom_Category_Name>Type Helpers</Custom_Category_Name>
     <Custom_Category_Icon>[...omitted...]</Custom_Category_Icon>
     <Controls_Palette_Information>
       <Virtual_Palette_Base_Path>Controls</Virtual_Palette_Base_Path>
       <Palette_Disk_Base_Path><menus>\Controls</Palette_Disk_Base_Path>
       <Syncing_MNU_file/>
     </Controls_Palette_Information>
     <Functions_Palette_Information>
       <Virtual_Palette_Base_Path>Functions\MEI</Virtual_Palette_Base_Path>
       <Palette_Disk_Base_Path><vi.lib>\MEI</Palette_Disk_Base_Path>
       <Syncing_MNU_file><menus>\Categories\MEI\dir.mnu</Syncing_MNU_file>
     </Functions_Palette_Information>
     <Apply_Short_Names_to_VI_Titles>false</Apply_Short_Names_to_VI_Titles>
   </Palette_Sets>

 

I think Palette_Disk_Base_Path is wrong - it should point to <menus>\Categories instead. Obviously I can just hack the .vipb file, but how would I change this in VIPM? Or is this a bug?

 

Edit: Wonky formatting.

[Mangesh]

I am using the free version of VIPM 2013.0.0 (Bulid 1878). When I make my own custom package using the package builder, the spec file that is generated is placing the palette menu items in <vi.lib>, instead of <menus>/Catagories:

 

[File Group 1]
Target Dir="<vi.lib>/MEI/Type Helpers"
Replace Mode="Always"
Num Files=1
File 0="functions_mei_lib_binary_string_helper.mnu"

[File Group 2]
Target Dir="<vi.lib>/MEI/Type Helpers"
Replace Mode="If Newer"
Num Files=1
File 0="dir.mnu"

 

When I install the package in LabVIEW 2010, I can see my palette on the function palette. However, when I install on LabVIEW 2012, I see nothing on the function palette. If I copy the menu items from <vi.lib> to <menus>/Catagories, then I can see this in LabVIEW 2012. For some reason, LV2010 is way more tolerant with dodgy menu installs than 2012 is.

 

Here is what my palette set looks like in my package's .vpib file:

 

    <Palette_Sets>
     <Palette_Set_Name>MEI</Palette_Set_Name>
     <Use_Custom_Category>true</Use_Custom_Category>
     <Custom_Category_Name>Type Helpers</Custom_Category_Name>
     <Custom_Category_Icon>[...omitted...]</Custom_Category_Icon>
     <Controls_Palette_Information>
       <Virtual_Palette_Base_Path>Controls</Virtual_Palette_Base_Path>
       <Palette_Disk_Base_Path><menus>\Controls</Palette_Disk_Base_Path>
       <Syncing_MNU_file/>
     </Controls_Palette_Information>
     <Functions_Palette_Information>
       <Virtual_Palette_Base_Path>Functions\MEI</Virtual_Palette_Base_Path>
       <Palette_Disk_Base_Path><vi.lib>\MEI</Palette_Disk_Base_Path>
       <Syncing_MNU_file><menus>\Categories\MEI\dir.mnu</Syncing_MNU_file>
     </Functions_Palette_Information>
     <Apply_Short_Names_to_VI_Titles>false</Apply_Short_Names_to_VI_Titles>
   </Palette_Sets>

 

I think Palette_Disk_Base_Path is wrong - it should point to <menus>\Categories instead. Obviously I can just hack the .vipb file, but how would I change this in VIPM? Or is this a bug?

 

Edit: Wonky formatting.

 

Hi,

 

I could not recreate this issue.

 

Can you please explain how do you get this .

 

One more think what "Base Path" you are providing in destination Tab http://screencast.com/t/slb7Fo57

 

Also if possible please provide the package that you are trying to build.

 

Thanks,

 

Mangesh

[AMP]

Ah, never mind - user error. I had an old custom install (before VIPM) that was causing some confusion with the menus. I removed the old install and built a new package in VIPM, and everything is working as intended now.

[Michael Aivaliotis]

Awesome, great to hear! Have a great long weekend.