Jim Kring

Ah, thanks. There was an indexing off by 1 error

Ah, OK. Is it the procurement (funds) or the process of validation of new tools that holds things up?

Great idea, Joerg. This is not currently a feature, but it's worth considering, for sure. Your use case sounds valid.

Ah, OK. I'm curious if there's anything holding you back from upgrading to VIPM 202x?

Sounds interesting. I'd be curious to learn more about what these Vis do specifically (or even a hypothetical example). I'd also be curious about whether the toolkit could actually be packaged into a VIP. We've been exploring better compatibility with PPLs. Maybe you could share some details (even offline if you prefer).

Or you could think about it like... - now your projects can more easily use different versions of packages - now each of your projects can decide whether to install packages globally or locally in the lv-venv

Great question. Yes, it's recommended to not have the same package installed globally and locally. It would be recommended to create a .dragon project for the projects that have global package requirements and keep the required packages in a .vipc for that project. Then, when you switch to those projects, you can install the required global packages.

We've seen this happening, too. It seems to happen only to the menus and its intermittent (more so on some systems). Are you working in a virtual machine?

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

This should be working better in build 2721. If you can, please test and confirm whether or not it's working correctly now.

There's a new build of Dragon and VIPM 2021 Beta: Download it here or via check for updates in Dragon/VIPM. Here's what's new (since the last build 2712): Fix - Installing packages with deep recursion (e.g. A>B>C>A) was getting stuck and hanging VIPM (e.g. SQLite toolkit). This has been fixed. New - VIPM Extensions for LabVIEW now adds support for various other palettes like Connectivity, Data Communication, etc. Fix - Detection of project LabVIEW version was not working well if there were no VIs in project. This has been fixed and the LabVIEW version will be read from the .lvproj file. Fix - Opening .dragon projects from Windows File Explorer via double-click was not working. This has been fixed. Fix - Drag & Drop of packages in the Resources Tree was causing problems. Drag & drop has now been disabled, since it was not implemented as a feature and was causing problems for users. Fix - If a Dragon project's VIPC file path (as specified in the dragon project configuration page) was missing from disk it was causing packages to not appear in the Resources tree. This has been fixed and a missing VIPC file should not cause problems -- it will be created as soon as a user chooses to add a package to the VIPC. New - The Dragon project configuration page now shows a dialog when a user un-checks the "Install Packages Under Project Folder" setting, asking the user if they want to delete the lv-venv folder from disk. This avoids installed packages in the lv-venv remaining on disk and project VIs linking to those lv-venv VIs. Fix - The LabVIEW Project window was sometimes showing (off to the lower right) when on the Resources Page and the window was maximized. This has been fixed. Fix - On German language systems, the LabVIEW Project ("Projekt") window would stay floating instead of docking inside of the Dragon project window -- this has been fixed. New - The dragon project dialog prompting users to install required packages now shows a list of package names/versions and the target installation environment (global or virtual) so that users have better understanding of what will happen when they choose to "Install". Previously, this dialog did not show package names or installation target. Fix - The Windows Desktop and Start Menu items for "Dragon" were not opening the dragon app. This has been fixed. Fix -- Right clicking on the empty area of the recent projects list of the Dragon Welcome window was causing problems (and should not be possible). This has been fixed and and its no longer possible to right-click on the empty area of the recent projects list (no right-click menu will appear)

Thanks for the clarification on your use case -- it's very helpful (and exciting) to see the code in action that does the automated builds of your VI Packages! We've done some work on a fix for this issue (we're calling it a "bug") and I'll ping you off-line so you can test it out, if you'd like.

Hi Joerg, Great idea. A couple comments/questions: I see that the VI Package Builder GUI defaults to 1 for the major version, yet it allows changing it to 0. It also allows you to build and install such a package (with 0 as the major version), just fine. More so, I see there are several packages in the wild (on vipm.io) that use 0 as the major version number, too. So, it would seem reasonable to allow the VIPM API to support this, too, and it wouldn't introduce any new problems. Which VIPM API VIs are you calling and how you're using it? I'm assuming you probably have an existing .vipb file and you're using "Read VI Package Build Spec.vi" and then "Write VI Package Build Spec.vi" to update a value such as the build number, as shown below. Thanks for posting the idea and for your additional input.

Hi Tom. The vipm.io credentials should work for you. If not, it may be an IT issue, which we've seen in some instances. I'll ping you off-line.

Hi Alex, This may not be trivial, although it's probably technically possible. I'll ping you off-line. -Jim

Ah, OK. Thanks @Sam Grayson. It's helpful to know that the issue may have something to do with .NET.

Those a great ideas, Patrick. One important point of clarification: The VIPC Editor does not provide any indication about what is currently installed. It only shows package states relative to the list of packages in the configuration. Also, about the current design/process: We're working to improve the workflows and visualization of information in the Resources tree. We still have a ways to go. Until then, we want to make opening the VIPC "easy enough" (it's only a right-click menu away), but we're intentionally not putting the "VIPC" button on the project sidebar, because we want to encourage people to use the Resources tree as the first place they go to manage the project's package dependencies.

Hi Patrick, This is a "rough area" that we're still figuring out the best way to visualize that there's a different version installed and whether it's in the VIPC. So, for now, we's showing both package versions. There are a couple ways to work this out, currently. In the Resources Tree 1) Right-click on 1.6 (which is in the VIPC but installed) and choose "Remove from VIPC" 2) Right-click on 1.8 (which is installed by not in the VIPC) and choose "Add to VIPC" In the VIPC Editor 1) Right click on (A) the Resources navbar button, (B) the Resources node in the tree-view, or (C) the lv-venv node in the tree-view and choose "Open VIPC File" - this will open the VIPC in the VIPC Editor Window. 2) Right-click on 1.6 and choose "Change to Version >> 1.8" or another version of your choosing. Please let me know if these answered your question and whether they work for you, or if you have any additional thoughts/questions about this workflow.