06-12-2017 05:33 AM
Hello,
I'm building a software product that is growing and this with VIPM. The build process in VIPM is easy and thus a bit limited to what I can get out. I'm listing the hierarchy of what I get and what I want. When I select to have a Custom Category I can put my Company name here and get a nice palette where I can install all my packages. However, I do want another subdirectory so that I can have a product built up of several packages and they would show under one product family under my company name category. Now all my builds just gets flat under the company name category. I've tried a few things for example to name the Product Name the same for those I want in the same folder, but this results in several subpalettes with same name but different vi's within.
Any suggestions?
What we get
Addons
Company name (custom category)
Product Name 1(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
Product Name 2(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
Product Name 3(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
…
What we want
Addons
Company name (Customer Category)
Product Family name (folder for other packages to be installed in)
Product Core name 1(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
Product addon name 2(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
Product addon name 3(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
Product Family name 2 (folder for other packages to be installed in)
Product Core name 4(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
Product addon name 5(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
Product addon name 6(name of Functions palette for seperate package)
Func.vi
Func.vi
Func.vi
Solved! Go to Solution.
06-15-2017 03:42 AM
I've managed to find somewhat of a solutions to this problem now.
If I first build a package just including a placeholder.vi (you need that to be able to build) and have this as a dependency for all your other packages. This package will create your company Custom Category and as the palette will be empty their wont be any mnu file loaded in the palette.
Then on your core product family package you use a custom category with the product family name and icon. For addon packages to this product family don't select a custom category but browse to Company Name>>Product Family folder and then you will have layers of folders.
Another solution is to make your own .mnu files and include this in source file settings.
Any other suggestions?