What's New in VIPM 2020.3
VIPM 2020.3 is a Maintenance Release with bug fixes -- see VIPM 2020.2 release notes.
It is recommended that all VIPM 2020 users on Windows and Mac upgrade. Note: A Linux build of VIPM 2020 is not yet available.
Improvements in this Release
- Package Building Improvements
- Palettes can be added to the Palettes of other Package's - VI Package Builder now builds packages such that all of their palettes (and subpalettes) are targetable by other packages (meaning: other packages' palettes can be installed into your package's palettes). This is useful when a “child” package extends a “parent” package’s functionality and the child’s palette should appear as a subpalette of the parent. Note that this will require rebuilding the parent package in VIPM 2020.3, in order for the child package to target the parent's palettes.
- Palette Browser Shows all Targetable Palette Locations - VI Package Builder’s palette browser tree view sometimes would not show all targetable palette locations (specifically if an targetable palette’s mnu file was in a folder with a dir.mnu)
- Windows Stability Improvements
- VIPM Browser System Tray is Now Optional and Disabled by Default (configurable in the Options Dialog) - The VIPM Browser System Tray (Windows Only) is now DISABLED by default. You can re-enable it from the VIPM Options dialog on the General settings page. The System Tray feature enables VIPM to start up faster, but it was causing some issues (hanging of VIPM) on some users’ Windows OS installations. Now, you can enable or disable this feature as needed.
-  Clicking on the pinned VIPM icon in the Windows taskbar should always open VIPM -- it was not opening if VIPM Browser was running in the System Tray. This has been fixed and now VIPM correctly opens when you click on the pinned VIPM taskbar icon (and/or when you run "VI Package Manager.exe" from the installed location).
- Other Improvements
- Auto-switch LabVIEW Target only when VIPM Browser is open - VIPM no longer automatically switches to the active LabVIEW version (the one actively being used in Windows by the user) unless the VIPM Browser window is open. The auto-switching was causing issues for some users working in multiple LabVIEW versions (building packages in one version and testing in another).
-  Case Sensitive Package Repository URLs - Repository URLs were being coerced to lowercase when added. This has been fixed and the case is now preserved.
- VIPM for Mac (macOS) Improvements
- Works on macOS 11 Big Sur (rudimentary support with work-around)
Minor Patch Builds
- MacOS - Fix for issue with packages containing read-only files.
- MacOS - Fix for issue with packages containing files having brackets (e.g. "[" or "]") in their filename.
- Windows - Fixed issue on Windows where VIPM would auto-start when LabVIEW starts, even if System Tray is not enabled. VIPM should not auto-start if System Tray is disabled.
Article is closed for comments.