Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 12/17/2020 in all areas

  1. I think I see what you're saying -- if an older version of the package is published in a repository, but the installed/latest (i.e. displayed) version is not published, it would be helpful to know that it's a development version that's not yet "officially" published to the repo. This is different, perhaps, than a package where no versions are published. Idea: Maybe VIPM should display "Local" as the Repository name if no versions of the package are published. This deserves some more thought, for sure. I'm glad you have a workable solution, for now. Thanks for sharing these ideas.
    2 points
  2. Some packages (specifically if using NI License Manager API) require VIPM and LabVIEW to be started as administrator. It'd be great if there would be a "requires admin rights" flag for the package.
    1 point
  3. Hi Ivan. Yes, VIPM checks the package integrity. I think it must be an issue that VIPM Community is not running the post-build custom actions. I'll have our team look into this as well. I'll ping you offline about how we can get a work-around for you.
    1 point
  4. This is very small issue, but anyway let me post it here. It would be nice to set scrollbar in the list to the start position, when the view is shown. Because now it happens that, for example: user opens "New Releases" view; scrolls down; presses "Go back"; presses "Most Installed" button; Most Installed view is opened, but the scrollbar is set to previous position as it was at "New Releases" view. And it could be a bit confusing, because if user does not notice scrollbar position, he could think that those items in the list are the top one, but indeed th
    1 point
  5. Hello @Jim Kring, thank you for the provided files for unpack/repack the package. I've tried to implement post-build action, but seems that there are 2 issues. 1. Seems, that post-build action is not executed. I've put breakpoint to post-build action VI - and nothing happened during the build, VI was not executed. Also, spec file was not modified. Could it be the bug, and post-build action is disabled for Community edition (the same situation as with flags?). 2. I've prepared VI in order to modify package manually (as post-build action was not called). When I
    1 point
  6. OK, I think we're getting closer to figuring this out. It appears that when VIPM Community is activated the Restart LabVIEW setting is not being applied correctly to the built package settings -- this is a bug. It'll file a bug for this and have our team look into.
    1 point
  7. Hi @Jim Kring, thank you for update; I'm going to try that post-build action. This build was done using Community Edition (and I'm working on open-source toolkit). Did you check please that this option is really set in spec file? But maybe if you use another build, that issue does not exist there already (I have VIPM 2020.3, build 2540). Thanks a lot for your help!
    1 point
  8. Thanks for that extra info @kosist. We're going to look into this much deeper, but I wanted to give you a quick response with a possible work-around. If you create a post-build custom action (Note: This requires VIPM Pro or VIPM Community, and won't work with VIPM Free) you can unpack the package (meaning: unzip the .vip file to a folder), modify the spec file (set the "restart labview..." key to TRUE), and then repack the package (zip it back up into a .vip file). Please let me know if this makes sense or if you need help. Here's a screenshot of how you would call this in your
    1 point
  9. Hello @Jim Kring, sorry for the confusion, have no idea why I've written like that... What I meant - is that LabVIEW is not restarted after toolkit is installed. I'll update original post, sorry for that. I've checked spec file as you've suggested, and really there is set "FALSE" flag for LV restarting. Let me show the screenshot of toolkit's configuration, and resulting flags in spec file. Let me also attach dummy package which reproduces the issue. Thank you very much for your help! Restart Issue Toolkit.zip
    1 point
  10. Let me share the following idea. It could be nice to extend VIPM login feature in a way that it would allow to store list of installed packages based on machines, and LabVIEW versions. When user is logged in - he could create such configurations, and synchronize them across machines. Configuration could be stored online, along with credentials used for VIPM login. It could allow then to login into VIPM, see and install missing packages on the particular machine. I know that it is possible to create vipc files, but anyway this does not guarantee that package configuration file wi
    1 point
  11. What is the format for the "Types and Defaults" input?
    1 point
  12. Thank you @Jim Kring, now it is clear.
    1 point
  13. If user has claimed toolkits on vipm.io, there is visible button "Release New Version" at the toolkit's home page. What does it actually do? Does it allow to immediately publish the updated version of the toolkit, or it sends it for the review to NI? Because now in order to do update of the toolkit we could also send it via special form to NI, they do some brief review, and then publish updates. Does "Release New Version" do the same thing? Or, it depends on the type of repository where the toolkit is hosted - like, if it is hosted at LabVIEW Tools Network repository then we need to
    1 point
  14. That button/form is for publishing open source packages to the VIPM community repository. Some of the packages on VIPM.io are hosted on the NI tools network repository. You’re right that those buttons should probably be disabled for commercial packages hosted on the NI tools network.
    1 point
  15. Currently at our company we are building internal toolkits which we use for projects, but do not put it to LVTN. Toolkits are published via OneDrive, everyone has mapped same local folder as repository in VI Package Manager. Different toolkits are handled by different developers. And sometimes there is a situation, when new version of toolkit is built, installed locally and tested, but it is not published to our local repository. It would be nice (I understand that on the other hand it is not such a common case) to have it in such a way, that: - developer installs new version of
    1 point
  16. Hello @Jim Kring, thank you, actually yes, it is already displayed as "Unpublished" in the "Repository" list. Just, this status is displayed also for toolkits which have never been published - for example, toolkit's development is in progress, and it is just installed locally in order to check how it works. The same happens when it is installed via VIPM which does not have license to publish packages. Or, when there are installed toolkits (like ESF, Dictionary, etc.) downloaded from somewhere, and which have not been published also. But nevermind, and thank you for the idea - it is p
    1 point
  17. Thank you @Jim Kring, happy to hear that ))
    1 point
  18. There has been some problems with the whole installation. Therefor I tried to do an update. There was updates but when I tried do install it the installer said "Another installation is in progress. You must complete...". I checked running processes. Restarted computer. Nothing helped. What can I do?
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.