Jump to content

kosist

Members
  • Content Count

    76
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by kosist

  1. Not sure that it will be possible to replicate the issue, but let me please describe how did it happen. For our package we have setting "Bind menu palette to library". And at the end of the build, VIPM starts to search "*.mnu" file (not sure that this is also normal behavior). Then it can't find it, opens dialog window to select it - but as it does not exist yet, we usually just close that window, and build is finished. Yesterday I've started the build on PC, and came back to it just today. So build was "active" around 21 hours (not sure that this is important, but point is that dial
  2. Release notes are written in the build specification. When, for example, developer realizes that some note should be added - package has to be rebuilt. But sometimes build of the package could take a lot of time (for example, build of our DBT toolkit takes approx. 1 hour with licensing, password protecting and further build). It would be great if there will be option to update just release notes, or another information which should not be compiled (authors list, etc.). That would help to save some time... But on the other side, developer should pay some more attention to build configurat
  3. I've seen similar behavior during building of LabVIEW application installer. We've installed LabVIEW 2019 some time ago, and then cleared NI Packages cache. Then later on we had to build executable and installer. Executable was built without issues, but with installers were problems - LabVIEW "asked" to provide installation media for various distributions/drivers, including VIPM Run-Time Engine (which had nothing to do with our application). Reinstalling VIPM didn't help. In our case, the solution was to repair LabVIEW completely, using installation media.
  4. Somehow post was posted twice, so I've edited second copy with this message, please ignore it...
  5. Great idea! Especially useful for packages for which it takes long time to install - because usually error caused by non-admin rights is dropped at the very end of the installation. But if it could warn user before the install - then some time could be saved. And also, sometimes it could happen the situation that: - LabVIEW is not running; - VIPM is launched; - toolkit is installing -> VIPM launches LabVIEW; - installation fails because of non-admin rights; - user closes VIPM, but LabVIEW remains to be running; - user launches VIPM as admin; - toolkit
  6. 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
  7. I've navigated using VIPM Browser as the following: Launched VIPM Browser. Pressed button "New Releases" (but it is valid for other buttons "Most Starred", "Most Installed" also). Clicked on the package in the list. Pressed "Go back" - and it returned me to start screen. It would be nice that it would return user to previous screen (like in my case - to "New Releases" screen).
  8. I've tried to press "New Release" button in VIPM Browser, and noticed the following. After it has retried information (it took some time, but I guess that's OK) - first time I've seen the same list as at vipm.io. Then I've pressed button "back" in the left upper corner, and then again button "New Release". And then it showed something completely else: So there was toolkit which is installed internally, and is not published. Also, there are items without names in the list: When I click on that row, it shows details window which is empty. Could it be those so-called
  9. 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
  10. 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!
  11. 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
  12. I've tried to build package using VIPM 2020.3, and set option "Restart LabVIEW After Install". Package is built without issues, but when I install it - LabVIEW is not restarted. Previously I was using such option with VIPM 2019, and everything worked fine... Am I missing something please, or this feature really does not work now? Thanks a lot in advance!
  13. 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
  14. 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
  15. 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
  16. 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
  17. I've tried it and it works as expected - so it is possible to browse external links without leaving vipm.io. Thank you for this change!
  18. I'm not sure whether this place is proper for this idea, but as vipm.io directly relates to VIPM itself, let me write it here. The point is that now toolkit could contain some links in the description. It would be nice to open them in new tab, and not in the current. This is small detail, but it actually makes users leave vipm.io while browsing some toolkit's homepage, or something. Of course, there are many ways of how to open link in new tab, but I guess it would be nicer that this would be the default action on simple left-click.
  19. Thank you @Jim Kring for the KB and for the suggested workarounds. We were considering the option of adding toolkit directly to source, but then decided simply to get rid of it completely since we've used it just as simple DVR-based lookup table. Moving to Tree Map was not possible, because it supports LabVIEW 2019 and later, but our project is done in LabVIEW 2015...
  20. @Paul Cardinale, what browser do you use? I use latest Chrome, and no issues with that. Try to clear all the cache from the browser, sometimes it helps (I had similar problems with another website).
  21. I've faced this issue while building our internal toolkit, and now it was possible to replicate it with dummy project. There is Tree toolkit which is unpublished in VIPM repository, but it is possible to download and install it from NI forum. I've created project which includes VI from examples for this toolkit just. As it is unpublished, I was trying to add it as internal dependency - so from Package Build configuration first scanned the project for dependencies, then this toolkit was added there, and then I've removed it manually. But following error occurred during the build (on t
  22. Thank you @Jim Kring. In my case, I would not use it often. Just, for example, recently I was curious to find out how many toolkits use ESF toolkit (which is unpublished, but possible to download from NI forum). So I knew about one toolkit which was built based on ESF, but had no idea about the others. But now when I think it through, I can not find other cases when I'd need to check dependent packages - unless to find out which package is used in other toolkits, or in other words how much popular that toolkit is, or something like that...
  23. Just the idea - not sure whether it is possible to implement. There are some packages, which are used as dependencies in other packages. And, we can find dependencies of the packages by sending package to configuration; but we can not find packages which are dependent on some particular packages. If we could do something like right click on the package in the list -> Find dependent packages, and it would show us list of packages (ideally even not installed) which use that package as dependency, that could be sometimes useful. Now, for example, we use some package as dependenc
×
×
  • Create New...

Important Information

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