Note: Other release notes can be found here.
What's New in VIPM 2011.0.1
12969: Prevent VIPB from creating package names with invalid characters
A change was made to the VI Package Builder interface to prevent VIPM from creating package names with hyphens and periods. These are invalid characters and cause problems during the package installation process. In addition, certain changes were made so that VIPM now handles package names that contain hyphens and periods in a more robust manner (for legacy packages).
12227: VIPM Crashes (immediately exits) on startup if no LabVIEW versions are installed
There was an internal error that was generated when VIPM would start up and the user had no LabVIEW installed on the machine. This would cause VIPM to exit immediately upon startup. - This has now been fixed. VIPM continues to launch in this case and displays a message describing the condition.
12259: Packages can be installed on incompatible labview versions (should not be possible)
There was a condition that allowed packages to be installed on LabVIEW versions that were incompatible for the package. - This is now fixed.
12365: VIPM gives odd feedback and fails silently when trying to install mutually conflicting packages
The root cause is that VIPM is allowing you to install packages that either themselves have a conflict with each other or with one of the dependencies of other packages. The Package action confirmation dialog lists packages as both having to be installed and uninstalled at the same time. Also, VIPM cannot act upon this condition correctly and fails.
Ideally, we would want to prompt the user and have them resolve the issue by selecting the packages they want to install and proceed with only those. However our current UI is not equipped to handle this. We are working on an improved user interface to handle this situation in the next full release of VIPM.
To improve the current condition and avoid confusion right now, we've added a check to determine if VIPM gets in this mode and present a message that gives the user an explanation and some suggestions.
12465: VIPM Crashes To Desktop from Splash
Related to Case 12227. - This is now fixed.
12475: Timeout setting of LVTN connection uses ms instead of seconds.
The timeout value used for connecting to the LabVIEW Tools Network was incorrectly using seconds from the Options>Network>TCP/IP Timeout field without converting it to ms. - This has been fixed. Now the TCP/IP Timeout filed value is correctly used by the LabVIEW Toos Network interface.
12494: Category Icon Missing in Controls Palette
When installing packages that have a controls palette and use a custom category, The default icon is used for the palette instead of the defined one. - This is now fixed and the correct category icon is used in the controls palette of an installed package.
12417: Mass compile does not work sometimes.
Mass compile did not work sometimes. - This is now fixed.
12351: Color issues under XP with product information cell
There was an issue where under certain color themes in Windows XP, you could not view the product information cells of the LabVIEW Tools Network viewer. - This is now fixed.
11859: 'Make toplevel in llb' should be disabled for non-VI files.
This is now fixed. When you click on an item which cannot be marked as a toplevel inside of an LLB, the "Make top level in LLB" checkbox is unavailable.
12883: Some VIPM dialogs are garbled.
Under Windows and using "Large Fonts" settings, some VIPM message dialogs had overlapping text and showed other garbled text on the screen that should not have been there. - This has now been resolved.
Article is closed for comments.