Jim Kring

The hover effect does not show when the VI is in Edit Mode. It should work OK when the VI is running or when it's in Run Mode (tip: use <Ctrl+M> to toggle between Edit and Run mode).

Shoot. That setting was my secret weapon. Now, I'm not sure what it could be... If you're interested, you might try VIPM 2020 Beta and see if that fixes things. It's pretty stable at this point and we're actively fixing issues.

Thanks for posting to the idea exchange and letting me know more about your packaging use case. > Side question: Any idea why Chrome freezes will VIPM is processing a (very) large package? I'm not sure, but Chrome can use a LOT of memory with lots of tabs open. It could also be related to disk usage. I'm not sure. 🤷‍♂️ > over 1200 defined messages. Since LabVIEW does not support sparse enums Hmmm... Maybe you could create your own non-sparse enum that you pass into your VIs and then use a conversion VI with a look-up table to convert these non-sparse enum values to the sparse integer values used by your low-level library. This is discussed a little bit here on lava.

One thought I have is that you might try the Options >> Network >> Configure Proxy to Access the Internet setting. Try testing VIPM with either "Use System Proxy Settings (Windows Only)" or "No Proxy (Direct Connection)" -- that can sometimes make a difference. PS - Your options page might look a little different, since I'm using VIPM 2020 beta. 😉

VIPM Browser The "VIPM Browser" window (below) is new feature that provides a fast way to search and install packages. To open the VIPM Browser, do any of the following: Click on the Windows Start menu and type "VIPM Browser" Double-click the "VIPM Browser" desktop icon Double-click on the VIPM Browser system tray icon (which will be visible when LabVIEW or VI Package Manager are running) Right-click on the VIPM Browser Windows system tray icon and choose Open VIPM Browser Click on the Open "VIPM Browser" link on the VI Package Manager main UI Choose the Window >> VIPM Browser menu item in VI Package Manager's menubar. Search Type a search query and view the results. You can give a star to a package you like and see which packages have been given stars and installed by other users (along with some stats). Note: Only public packages can be starred and/or show statistics. Select a Package Install a Package Two UI Sizes: Big Mode and Compact Mode You can toggle between the big mode and compact mode by using the Collapse/Expand button. Small Mode The "small mode" is designed to not take up much space. Note: In "small mode", the VIPM Browser window will float on top of LabVIEW. It won't do this in "big mode" A checkmark indicates a package is already installed. Click a package to select it. Tip: Keyboard navigation You'll find that <tab>, <shift+tab>, and the <up>/<down> arrow keys work great for navigating the search results list -- give it a try. Once, you found a package, press <Enter> to select a package, install/uninstall it, and open it in LabVIEW Press <backspace> to go back a screen (until you get to the search results when backspace will start editing the search query) System Tray Icon The system tray icon tells you when VIPM Browser is running. It always shows when VI Package Manager is running. Note: when the VIPM Browser system tray app is running, the VI Package Manager UIs will open very quickly, since they don't need to be reloaded. The system tray icon runs when LabVIEW is running, and can even be configured to run when Windows starts up (right click on the System Tray icon and choose Options > to configure). See also: New Feature: Windows System Tray Notifications Download VIPM 2020 today!

That looks like a networking issue. I'm able to download that file on my computer. http://ftp.ni.com/evaluation/labview/lvtn/vipm/index.vipr Are you able to click the link above and read the file? Would you mind rebooting and trying again? 🙂

Can you check the error logs? C:\ProgramData\JKI\VIPM\error It'll probably be the last entry (bottom of the log file) in a file with today's date.

Thanks for the great idea!

I see what you're saying. Ya, this isn't an extremely common operation -- typically, controls are added to the Controls Palette and VI's are added to the Functions Palette. So, there is an Add Folder of Controls menu option on the Controls Palette editor and an Add Folder of VIs on the Functions palette editor. I'm trying to think of a simple solution to make this easier for you, and I can't think of one. A couple possibilities: - The Add Control or VI option could show a file dialog that allows selecting multiple files. - We show both the Add Folder of Controls and Add Folder of VIs right-click options on both the Controls and Functions palette. Maybe you could put in a feature request, here on the VIPM Idea Exchange.

Hi @jb1592. One thing you can do is to give the 32-bit and 64-bit DLLs different names (or keep the same names but put them into different subfolders) and then pass the path to the Call Library Function so that the DLL is loaded at run-time.

Hi Guys, That's a bit tricky and depends... The point of adding a name suffix is because LabVIEW has historically done a poor job of preventing cross-linking of files -- there was a global namespace for all VI's in memory. Since then (and recall that VIPM has been around for over a decade) LabVIEW added lvlib (and lvclass) files to help with namespacing. I'd say that the #1 use-case for adding the suffix/renaming is that when you're the developer of a tool, the installed version of that tool can mess up the development version of the tool. Of course, with the suffix/renaming you can get into situations where the source version of the tool accidentally links to the installed version, if you're not careful (since the installed versions will be in the palettes). As @HB65093 mentioned, when you're creating a Quick Drop, Project Provider or other LabVIEW plug-in, sometimes the renaming gets in the way of things working properly. And, as @hooovahh mentioned, the renaming messes up dynamic dispatch calls, since the VI name is critical for LabVIEW to identify the override methods. For me personally, there are many cases I do not add a suffix/prefix during the build process, but I usually leave this setting ON by default unless I want it OFF. @hooovahh - have you had any problems *not* adding the suffixes? If not, then it's probably not a problem. I'm really enjoying hearing from you all about what works well (or not) and why!

Glad you got this working and sorry for the delay in response.

Want to explore VIPM 2020? (and help us test all the new features) Update: You can get the VIPM 2020 Release Candidate here: Already signed up? Visit the VIPM 2020 Beta forum to get started with VIPM 2020. (Note: If you cannot access the above forum, your application is being processed)

You're going to love VIPM 2020 (sign up for the beta today!) 😉

Thats a good idea, Stefan! You can post it and any other feature ideas you might have in the VIPM Idea Exchange.

@Francois Normandin Can you create a very simple VI Package project that has an LVLIB with an RTM that reproduces this issue? This will simplify the debugging.

Thanks for posting this, @Francois Normandin. I'm happy to help debug/fix this.

Hi Scott, We're working with National Instruments on VIPM 2020 and this is a priority. Thanks for your patience, since there's a lot to do. Yes, we'll certainly want some help testing, once it's ready. I don't have an exact timeline at the moment.

Definitely before NIWeek in May 🙂 We do have a beta underway. Please LMK if you're interested to help test.

I've reproduced the issue and it should be fixed in VIPM 2020.

Hi @StefanLemmens. Thanks for the detailed error report -- that's really helpful. This has been logged in our system as ID 18607 and we'll be looking into it.

@ThomasGutzler @jamesmc86 @TomMcQ @hooovahh @drjdpowell We've been able to reproduce and fix this issue (ID 18605). It'll be fixed in VIPM 2020.

Hi. I just took a look in the latest version of VIPM and it's having some trouble building your package. Note: installing and calling VIs installed outside of LabVIEW is somewhat non-standard, so that's probably why it's not working too well. We'll need to do further debugging.

Ok, thanks for letting us know, Tim. Hope you got it working.

I can't understand why that's not working. Can you try restarting VIPM, refreshing the package list, and see if you get the same error?