Your comments
As far as I know. This layering feature is only available to VIs. I don't think this would work with palette icons, even with the new API. I hope I'm wrong.
13 years ago
Just to clarify. You want a single button install across all LabVIEW versions?
You can build packages with VIs that have the same name as long as these VIs are in different *.lvlib files.
I'd like to find out more about this idea and what people would like to see in the tree. Trees can get busy, quickly.
In your example with the OpenG Library. This is a package with dependancies. So you are asking that we list all the packages in the tree and show the dependency packages as child nodes. When clicking on the package in the tree, what would you see on the right hand side?
How about recently installed? Would this be useful as well?
Would additions only include local non-repository packages? There is a date which VIPM knows about which is the date a package has been added to the repository. Would this be what you're looking for?
Jonathan. So are you recommending this as a workaround? What's your opinion on the using the library as the source?
Can you suggest some alternatives?
How would you use this feature? Do you expect to right-click on a folder which contains your source? What would the menu say?
As mentioned in the cross-posted thread, VIPM can already do this using multiple palette sets. Each palette set can target a different LabVIEW palette category.
Perhaps there can be a way to easily copy or sync the palette layout from one palette set to another.
In VIPM. You can remove (exclude) VIs from the package build process. Is this not a workable option? And if not, why?
Customer support service by UserEcho
