Your comments
Hi Fabiola. No, this is not yet available, but I do think this is a great idea and I'd love to see that added to VIPM's feature-set.
Note that there hasn't been any work done on this feature, to date, so we can't make any promises about timeframe (and I've edited our last post with a retraction) -- I apologize for that.
Also, I've given this feature suggestion my vote :)
Note that there hasn't been any work done on this feature, to date, so we can't make any promises about timeframe (and I've edited our last post with a retraction) -- I apologize for that.
Also, I've given this feature suggestion my vote :)
We can't make any commitments about when future releases will happen and what features will be included.
Hi David. This is a fantastic idea! We've actually played around with this in our labs. One issue we ran into is that installing packages (applying dependencies) involves communicating with LabVIEW (mass compiling, refreshing palettes, etc.) and this can deadlock the project.open process (since that goes through the infamous "root loop"... or something like that). If we could only give an indication that the VIPC needs to be applied (but require that you apply it yourself), would that still be helpful? Thanks again for offering your great ideas!
As a work-around, did you know that you can drag & drop VIs from Windows File Explorer? Does that help speed things up?
Customer support service by UserEcho
Hi Joerg,
This should be possible with a post-build custom action VI.
(it's still not a native feature)
-Jim