kosist

Thank you @Jim Kring, happy to hear that ))

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!

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.

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...

@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).

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 the screenshot). It could not copy and save method "To Variant.vi", because VI with the same name already existed in the target folder/memory. That method is dynamic dispatch method, which is overridden in multiple classes (on the screenshot). Is there a way to configure build somehow so VIs will be moved to subfolders to avoid name collisions (something similar as LabVIEW build has - that in case of "Always Include" classes it moves VIs with the same name to separate subfolders), or some additional prefix will be applied to its name? Or, root cause of this error is something else? In our case, in order to be able to build the toolkit, we had to remove Tree toolkit from dependencies, and implement functionality which we needed as custom library. We couldn't distribute VIPC with our toolkit, so that's why we wanted to keep all dependencies ether as internal (for toolkits which are not published) or let VIPM install them during installation of our toolkit (for toolkits which are published and available in public VIPM repositories). But that was just a workaround... Thank you very much, Sincerely, Ivan.

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...

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 dependency, and I was wondering whether there are some other toolkits which use it as dependency. But, there is no way to find it out - unless to check information for each of the package or trying to install them. Thank you very much, Sincerely, Ivan.

We've implemented the following solution. One Drive is mapped to the same location on all PCs (Public Documents), and we have shared one folder as repository folder. So we could publish packages to that location from any PC, and scan it as VIPM repository. Thank you for your help, Sincerely, Ivan.

Thank you very much! I've already tried that (added URL directly to ini file) but it didn't help. I guess there is really issue with Dropbox. Most probably we would do the following - add OneDrive (or Dropbox) folder to the same locations on all our PCs, and then treat them as local repositories...

Is it possible to add Dropbox/OneDrive shared folder (by link) as repository using "Repository Manager" window? It allows to select just local folders. When I've tried to change it to public url and publish the package, it didn't work... My point is to create repository from which we could download toolkits internally in our company. What is strange, that VIPM changes URL to lower case letters - so url of Dropbox shared folder is not valid anymore, because it has upper/lower cases, thus making it as lowercase change URL completely. Thank you very much, Sincerely, Ivan.

Hello, let me report the following issue, which was discovered by my colleague. We use LabVIEW 2015, SP1. JKI Design Palette v1.0.5.196. We have some project, which has dialog windows. And we've noticed, that sometimes when user did right-click on VIs title bar, LabVIEW is completely frozen. Then we've started to investigate the issue, and found out that Path control from JKI Design Palette causes high CPU usage -> which somehow in its turn causes issues with title bar context menu. When we have just 1 empty VI opened, CPU usage is low, around 1-2 %. But as soon as we place there Path control, CPU usage jumps to 22-30%! And VI is just opened, it is not running. When we place any other path from "native" LabVIEW palette, CPU usage is around 2-5%. Thank you, Sincerely, Ivan.

Is it possible to export list of used packages from package configuration to some text file? The point is, that I'd like to include list of packages into the documentation - so now I have to write list of packages manually, based on the list which I see in VI Package Configuration Editor...

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.

Let me update this thread with new inputs. I've found error logs for the toolkit (I guess this is some new feature). And it says the following: Which network it tries to reach? Could it cause that crash? I have active internet connection, so that should not be a problem...

In case if someone needs download link for VIPM 2019, here it is - http://traffic.libsyn.com/jkinc/vipm-19.0.2029-windows-setup.exe. I've found it in "C:\ProgramData\JKI\VI Package Manager XXX\updates\vipm-update.aiu" file. UPD: VIPM 2018 is accessible by this link - http://traffic.libsyn.com/jkinc/vipm-18.0.2027-windows-setup.exe VIPM 2017: http://traffic.libsyn.com/jkinc/vipm-17.0.2007-windows-setup.exe

I can't because pro license has limited time of support. Like, one could use license to build packages, but there is no support after 1 year. Yesterday I've tried to install VIPM 2020 to another folder - but it didn't help; anyway older version was uninstalled. And moreover, now it is not possible to find installers for older versions online... So quite interesting situation - one could install VIPM 2020 by mistake, and then there will be no possibility to install VIPM 2019 (for example), because installer of VIPM 2019 is not on JKI website anymore (at least it is not possible to find it). And that's it - not possible to use Pro license, because there is no supported VIPM version.

When I search for JKI VIPM package using NI Package Manager, it shows two versions of the tool: 2019 and 2020. But when I select 2019, it anyway installs VIPM 2020 version.

Is it possible to have installed on single PC 2 versions of VIPM? The point is that we have VIPM 2019 which has Pro license (since 2018), but now when I've installed LabVIEW 2020, it is not supported by VIPM 2019. And if I'll update it to VIPM 2020 license will be invalid already. Is it possible to install the newest VIPM software along with VIPM 2019?

Thank you for your reply! Somehow yesterday I didn't realize that Edit could be used as Write, thank you. Glasses for reading will be great, this is similar as default accessors icons for VIs. I implement VI for CAN communication with some custom protocol. Thus I would like to read/write message by address, and send/receive command (or payload). Interesting is, that even Silver buttons set do not have such icons - although there are different kinds of icons. Regarding crashes - I've found out that on first call, after project is opened, it works for me, so I take all buttons which I need, and then work with application 🙂 Most probably, I have something with my LabVIEW installation (different toolkits, drivers, etc.), thus something could be wrong there.

I try to use the toolkit when it does not crash 😉 and enjoy it a lot, but I've just found that there is no buttons with icons for such often used actions as Read, Write, Send, Receive. Also, there could be more "specialized", like Query, Execute, Init, DeInit, etc. Are there plans to expand the toolkit, or there is some specific reasons why those (at least more common Read/Write, etc.) are not implemented in the toolkit? Thanks a lot, Sincerely, Ivan.

Dear JKI community, let me, please, share the following - button "Boolean--Home-House-40x40-Button-(flat)" has label "Pause 23". Thank you very much, Sincerely, kosist.

Currently I use LabVIEW 2017 for my ongoing project, but I will give a try for LabVIEW 2018.

Dear Jim, I've tried to open it manually. When I run Start.vi in the lvlibp, then the same error occurs. When I open "JKI Design Pallete.vi", it is not broken. But when I run it, the following error occurs (Scan string error). Also, I guess that this error causes LabVIEW crash (or, reason for LabVIEW crash is causing this error). I don't know, if dump file could help you, but let me attach LabVIEW crash report - maybe you could take a look on it please? 3ed54b83-8458-4358-92a6-e275e35f5894.zip

Dear Jim, sorry for replying so late. I use Windows 10; and I beleive that it is not related to user rights. Actually, it works or not from time to time. Once I open LabVIEW - Design Pallete works; then I open some another project - it does not. For example, I open new VI, and load Design Pallete. It works fine. Then I close VI, don't save it, and open project. Call Design Pallete again - it does not work, that error is dropped. I close project, open empty VI, call Pallete - still error occurs. I close LabVIEW, start it again, open VI - Design Pallete works. Could it happen, that there are some in-memory dependencies conflict? Maybe pallete can't be loaded because lvlibp loads its VIs with the same names, which are already in LabVIEW memory? Upd: sometimes it works with the same project. Thus, most probably it does not related to dependencies... Thanks a lot, Sincerely, Ivan.