Note: Other release notes can be found here.

What's New in VIPM 2013.0.1

Download VIPM 2013.0.1 here: http://jki.net/vipm/download

New Features and Fixes

• Case 14965 - Custom password in VIPB >> Library Protection is not saved. In VI Package Builder, under Licensing and Activation > Library Protection, If you use Custom password setting and enter your own password into 
  the "Password*" field, it is reverted to "password". This has now been fixed.
• Case 15065 - Clicking "Cancel" reverts the palette to default. If you select to create a new palette set and then click cancel on the palette name dialog, the palettes would revert to default. This has now been fixed.
• Case 11551,14552 - The VI Package Builder UI incorrectly removes a package from the package dependency list if the user manually edits the version of that package in the VIPC file. This issue is now resolved. Now, if you change the package version in the VIPC file, after you perform dependency scanning, VIPM correctly uses the new changed package version as a dependency.
• Case 14474 - In the license and activation tab in VI Package Builder, If you clicked the browse buttons, VIPM would browse to the default folder instead of the previous license file path. VIPM now browses to the previous license file path.
• Case 14741 - Previously, auto-mass compiling of VIs after installing a package took a significantly long time to complete. We are happy to say that we've sped up the mass compile action. It is now at least 75% faster and will allow you to get to using your code, much quicker. Enjoy the speed improvement!
• Case 14779 - There was a certain configuration in the source files settings page of VI Package Manager, that would cause the the palettes to not build correctly. Specifically it was the 'Use Protection Settings of Parent Folder' checkbox. Unchecking this would cause the problem. This has now been fixed.
• Case 14785 - During package building, if you had subfolders in your source named with a single character, then some package configuration settings in the source files settings page would not be applied correctly. This has now been fixed.
• Case 14786 - Previously, the process of auto-mass compiling of VIs after installing multiple packages could (in certain scenarios) cause cross-linking of VIs between packages. This issue is now resolved.
• Case 14831 - On certain customer configured systems. When you try to edit the palette folder icon in VI Package Manager, VIPM would not open the icon editor. This has now been fixed.
• Case 14845 - "scan for dependencies" in VI Package Manager does not detect dependent packages in dependent VIs. This has now been fixed. If your package source calls dependant VIs that call VIs in installed packages. VIPM now detects the package dependencies correctly.
• Case 14846 - "scan for dependencies" in VI Package Manager does not restore removed dependencies. Previously, if you manually removed a package dependency, there was no way to restore it by doing a new scan. Now, "scan for dependencies" will give you the option to restore the previously removed dependency.
• Case 14765 - Fix for VIPM crashing on startup. This is the most important fix for this release and resolves a critical issue where VIPM would immediately crash and shut down on launch. This is now fixed. - This was reported by a number of users on mostly 64bit Windows OS. In order to fix the issue we had to remove certain functionality which is not critical to the operation of VIPM. Primarily, drag-n-drop of files from windows file explorer was removed. We will investigate the possibility of adding this functionality back in.
• Case 14553 - Saving in VI Package builder from the menu or using the keyboard shortcut Ctrl+S, would not save the package description information. - this is now fixed.
• Case 13839 - New feature. We've added the ability to add a help tag and a help file path to the 'Edit palette description' dialog. This dialog has also been renamed to 'Edit Documentation' to match the equivalent functionality in the LabVIEW palette editor.
• Case 14456 - "Remove Dependency" button doesn't work. In the VI Package Builder window, clicking the "Remove Dependency" button does nothing. It should remove the selected external dependency (and make it internal). - This has now been fixed.
• Case 14540 - Sub-nodes (files) forget settings in source files page. This is an issue affecting the source files settings page in the package builder window. When you specify a destination, other than the parent, for a file within a folder in the source files settings page, VIPM forgets this setting upon reloading the package source. - This has now been fixed.
• Case 14459 - Access license after package has been installed. This new feature will display a link in the package properties window which allows you to display the license file used by the installed package.
• Case 14444 - VIPM Package builder now filters out (ignores) folders beginning with .git. These folders will not display in the source tree and thus not get included in the package building process.
• Case 14458 - There is a new feature in VI Package building where you can set "Locked (No Password)" protection. This can be applied to source files at build time.
• Case 14088 - Make the build temporary folder a configurable path in VIPM. The internal temporary folder used to build VI Packages was set to a hardcoded path previously. Now it's configurable from the options. This allows fixing an issue where the paths are sometimes too long and would cause a build error.
• Case 14531 - Made some improvements to how icons are extracted from Xcontrols. Now when adding an Xcontrol to the palette editor (manually or auto-generating), it extracts the icon correctly.
• The manual proxy configuration mode was not working. This has been fixed so the manual proxy now works for those that use custom proxy settings to connect to the internet. The majority of the users should be able to leave proxy settings to default and should not require manual configuration of proxy settings.
• Fixed various typos and made some control descriptions easier to understand.