Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/06/2020 in all areas

  1. Some advanced users are asking for support to install VIPM for Windows onto a Docker container. This would allow creating fully automated build processes that spin up virtual machines that have LabVIEW and VIPM installed on them, so that VI Packages can be created automatically.
    6 points
  2. As an update, I have been applying the file directly to the unicodeStringtoASCIIJKI_Simple_Localization.vi. Arabic gets translated to ASCII correctly as shown in the screenshots. Maybe a kernel32.dll function needs to be updated. Hopefully I find something and I will post it on this thread.
    2 points
  3. With VIPM 2020.3 (build 2540) and VIPM API 2020.0.2.73, it's not possible to supply a major number of 0 via the API, the API returns an error 42: Seeing as we also build projects that are in a pre-v1.0 state, I don't see a reason to not allow the major build number to be 0. I was actually tempted to file a bug report... 😉
    2 points
  4. 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
    2 points
  5. 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
  6. 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
    2 points
  7. 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
    2 points
  8. Hi, I would like to ask for a help with the following issue: I am trying to distribute VIP file with some dependencies, which are not published on VIPM. Hence, I added them to VIPC and would like to distribute this VIPC with VIP file. Is this somehow possible?
    2 points
  9. Howdy V, I have not previously done exactly what you are asking, but have done some similar tasks. We use VIPM Pro and a local repository to distribute packages not found in the public repositories; not only our internally developed packages. First, using VI Package Builder's Destinations and Source File Settings pages you can easily include the file and specify where it is installed. Second, using the Custom Actions you can specify a VI to run Before or After the package install. Use the Generate VI button to create a template VI and save into your package project; I create a C
    2 points
  10. I do not know what I am doing wrong: I have an account on https://www.vipm.io/ where I can log in. I have VIPM installed and it was just recently automatically updated. I am able to install i2 JSON for 2018-64 I am not able to log in for "community" or "free" status. When I choose in the new window "Use existing JKI account" I get an error message, when using the account data for www.vipm.io. I also get an error when choosing "Sing up for a new JKI account". When pressing "Forgot your password?" an new tab in the browser opens where I can write my mail address and it tells
    2 points
  11. Hi, I am having an issue with functions palette I generate in VIPM. The palette is generated and behaves correctly in LabVIEW, however, when I click "show in palettes" in VIPM after installing toolkit, instead of my functions palette, Agilent 34401 palette is displayed. Any idea what might be wrong?
    2 points
  12. John, check out "Test Runner Pre-build action.vi" in the 1.0 release. I'm not sure what the current version is on LVTN, but you can find 1.0 on GitHub: https://github.com/JKISoftware/Caraya/tree/release/1.0.0/src The first snippet below is the Pre-Build action itself, the second is the actual guts of where the test gets invoked. Let me know if that doesn't get you started in the right direction or you have more questions.
    2 points
  13. I'd love to see these three License-related improvements to VIPM: 1) First, a main window column showing the package license, so it becomes very easy to see whether a package is open source, freeware, proprietary/custom, or something else. It'd be nice if the column title could be clicked to sort sort packages by license type: 2) To complement this, a change to the filter box with options to filter by license type, or maybe a second filtering box for this specific purpose. This would further help those searching for packages to focus on finding one they can afford and actually u
    2 points
  14. When adding contributors to VI Packages on vipm.io, the UI suggests that one can search for "vipm, github, and gitlab names": I tried that with one of my colleagues who is on GitLab but not on VIPM.io, but the search doesn't bring him up: Should this work?
    1 point
  15. Hello, Updating VIPM recently, I noticed strange caracters in update descripton (french OS). See below : I don't know if I'm the only one to get this, it's a minor concern, but I wanted to let you know (may it have other impact, perhaps on functionnalities ?) Regards,
    1 point
  16. One thing I didn't notice before, the library will only accept UTF-8 without signature. When a file is ran through with this encoding the file is accepted as an ASCII string through 'readUnicodeFileJKI_Simple_Localization.vi'. This works for Chinese and Russian, not for Arabic. If I try any other form of Unicode file encoding on the json file, the file will go through 'unicodeStringtoASCIIJKI_Simple_Localization.vi' that uses the WideCharToMultiByte function. It will however fail at 'JKI JSON Serilization.lvlib:Unflatten From String.vi'
    1 point
  17. Jim, as always, your elaboration is spot on. Here's a screenshot of what our tools do: So other than the fact that we write all the build numbers in one go (the whole cluster), it's what you described above. Thanks for taking the suggestion into consideration.
    1 point
  18. Cross posting here for visibility: Building a basic plugin-based application with HAL using JKI SMO, MGI Solution Explorer, and LabVIEW 2020 interfaces - NI Community Happy to answer any questions about the design process or application. Thanks for checking it out! -Nate
    1 point
  19. This was on a machine with only one version of LabVIEW/RIO ever installed on it - 2020.
    1 point
  20. 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
  21. 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
  22. 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
  23. What is the format for the "Types and Defaults" input?
    1 point
  24. 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
  25. 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!
    1 point
  26. With the latest VIPM update, VIPM opens whenever I start LabVIEW 2019. Is this really necessary? How do I stop this annoyance?
    1 point
  27. Thank you, Jim. I'll put it through its paces and let you know if I find anything noteworthy.
    1 point
  28. I believe that is what I was looking for. https://github.com/JKISoftware/Caraya/issues/112 It is coming in 1.2
    1 point
  29. Since there does not seem to be any actual security issue it could be just a waiting game. I think my IT department might be able to submit the executable for reevaluation or as a false positive, I will see if I can get it fixed that way. Thanks for the help.
    1 point
  30. I understand and I don't mind helping improve great products like yours. When I started the day yesterday, I opened LV2020 to work on one project. Upon completion, I closed LV2020. A few hours later, I had to work on another project that used LV2019. That's when VIPM opened and I closed immediately closed it. Finished my work in LV2019 and closed it. Later I had to open it again and VIPM opened along with it again. This morning during our initial messages. I opened LV2019 to make sure I was correct in my replies. I then close it and opened LV2020. That's when I noticed no VIP
    1 point
  31. I'm trying (and failing) to build a package for my Y Controls. When I run the VIPB file, sometimes it aborts claiming that a file or files are missing; but the files aren't actually missing and they aren't dependencies of Y Controls. Sometimes when I run it, I get no errors, but also no output. I would appreciate any suggestions. Y Controls.zip
    1 point
  32. Hi Ivan, You're right: Error 1357 during a package build generally occurs when two VIs of the same filename (but in different lvclass'es or lvlib's) are targeted into the same folder during the build. Fortunately, if the classes/libs (with the same-named method VIs) are stored underneath your VI Package's source folder then you can create a custom destination folder for each of them (and target each lvclass/lvlib with it's own specific destination folder). So, maybe you could move the Tree API into your project source folder. Then, you can have more subtle control over choosing
    1 point
  33. You're welcome and I'm glad we were able to find and fix a bug in VIPM. BTW, I had a typo in my response to you. I meant to say "I think they changed it so that you can no longer serve static sites/files over HTTP." Yes, some users have found success in having DropBox/Google Drive/Box.com/OneDrive replicate the repository locally as a network hard drive or folder, and then have each VIPM client reference it as a local repository. Let me know how that works for you.
    1 point
  34. Hi @kosist Thanks for sharing this question and feedback. At one point this worked with Dropbox, but I think they changed it so that you can no longer serve static sites/files over HTTP. I'm not sure about OneDrive. Basically, you'll need something that can host all the repository files as a static website. Regarding the issue where VIPM changes URL to lower case letters: There's actually a work-around for this. You can add the URL and then fix it in the VIPM settings INI file, as described here: [18866] Package Repository URL is coerced to lowercase when adding (should
    1 point
  35. Hi @James@Work. Thanks for posting about your experience with this. I'm sorry that JKI Design Palette was interfering with QuickDrop. Thanks for the good suggestion on including better documentation/instructions for how to work around this and for uninstalling it. I'm glad to hear it's working for you now.
    1 point
  36. In case when new (custom) destination's name starts the same as already existing one, then both destinations are treated as the same (not possible to edit name of custom destination, and when path is changed in one of them - it is reflected in another one). As the example, there is standard destination "Help Menu", then I've added "Help Menu Test" - both of them were treated as the same destinations. And then 3rd destination "Menu Test Help" was fine.
    1 point
  37. It would also be nice to have the shell menu option "Add to VIPM Library." on *.vip files and not only on *.vipc files. This way *.vip files can be added to the VIPM library from the windows explorer without having to install them.
    1 point
  38. A little more info I found when playing around: I located .mnu file responsible for my palette in LabVIEW directory and deleted it. Now, as expected, show in palettes does not work. Also, my palette disappeared from LabVIEW funtions palette. When I restore .mnu file, palette is available once more, however, show in palettes displays Agilent 34401 palette after clicking again.
    1 point
  39. Alin, Thanks for the detailed description of the bug. It helped me to reproduce it. I have recorded this issue as Case 18752 for consideration. I can't promise when this will be fixed but we will inform you when that happens. Since JKI State Machine Editor is open source, you can post any issues in GitHub: https://github.com/JKISoftware/JKI-State-Machine-Editor/issues Take care and stay safe.
    1 point
  40. Hello, I have exactly the same problem. When trying to sign in or create new account, I get the message as in the screenshot attached.
    1 point
  41. I don't see the way to "ignore dependency". Still looking through help.
    1 point
  42. Curious if there is any plan to ad LV2020 support?
    1 point
  43. Hello LV Gurus, I have used JSM since release 1.0 (circa LV 2011). I understand the sub-diagram label feature was not yet implemented. Is there a reason why the JSM 2018 still not using sub-diagram labels (like below) since that has been standard in LV for many many years. Thanks guys! Sub-Diagram Labels enabled (lots of manual editing just to clean up those comments) Sub-Diagram Labels not enabled (current 2018 version):
    1 point
  44. That did the trick. Curious - I thought that ran everytime you opened VIPM. Is that true? Does it only automatically do it on some schedule? I swear I had restarted VIPM.
    1 point
  45. Hi There! Glad you like the JKI HTTP REST client. For the base URI, I would use: http://192.168.0.100/restapi and then for the path when you call GET or POST, use: /relay/outlets/0/state/ Here's how you could add the X-CSRF header. Note that you can type (or copy-paste) new items into the drop-down selector for the header -- it works like a string control, but with some pre-defined options to make life easier for common headers. The JKI HTTP REST Client passes the username and password into the HTTP VI used by built-in HTTP Open Handle.vi, which I
    1 point
  46. You forgot one important thing: an asterisk "*" in the Machine Access List. Also, very important, verify your TCP port address in the VIPM (Options >> LabVIEW tab). If you have multiple LabVIEW installations make sure each VI Server have unique ports. Good Luck! Relativity1
    1 point
  47. Hello All! I'm working on integrating the Caraya test framework into our CI process. As of now, we are using a Jenkins server to manage our builds, but I'm looking to add our Caraya unit tests to that equation. I'm relatively new to the CI world, but have a good amount of experience using Carayas built in test reporting functionality (the text report version). Ideally, upon unit test failure I would like to have the full report sent to the user via email showing them which unit tests did not pass. I know some of this is handled on the Jenkins side, but I'm more so curious abou
    1 point
  48. 1 point
  49. It would be useful for quickly building palettes if the file dialog that appears after selecting the Add Control or VI option allowed multiple files to be selected. This would be especially useful if a folder contains a mix of CTLs and VIs, or a mix of items that are wanted on the palette and ones that are not.
    1 point
  50. For Windows: LVRunTimeEng.exe (see here for detailed installation instructions) For Mac OS X: LabVIEW821RuntimeEngine.dmg (see here for detailed installation instructions) For Linux: labview82-rte-8.2.1-1.i386.rpm (see here for detailed installation instructions) labview-rte-aal-1.1-1.i386.rpm Linux Installation Instructions (more info here): Run (must be logged in with root access for the machine) rpm -Uvh labview-rte-aal-1.1-1.i386.rpm Run (must be logged in with root access for the machine) rpm -Uvh labview82-rte-8.2.1-1.i386.rpm If the above links do not work then
    1 point
×
×
  • Create New...

Important Information

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