jgcode Posted December 18, 2010 Report Share Posted December 18, 2010 Steps to reproduce the bug (if it can be reproduced) Create Package A with a Custom Category palette and icon Install Package A Create Package B with the same Custom Category palette location, but change the icon Install Package B Expected behavior (what would happen if the bug didn't exist) Newer Package B Category icon is shown in the LabVIEW palettes Actual, observed behavior (the bug) Package A Category icon is shown in the LabVIEW palettes Here is a Jing Video demonstrating the what I am seeing: http://www.screencast.com/t/2QcthBoQAM After installing Package B the dir.mnu file is the wrong palette which can be seen from the date... ...as Package B's dir.menu's date is newer The Jing Video is too slow to catch this, but the process' logic says not to install the newer file as can be seen in the status update. Cheers -JG Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted December 20, 2010 Report Share Posted December 20, 2010 As far as I know. The new category icon should overwrite the old one. I'm looking into this. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted December 20, 2010 Report Share Posted December 20, 2010 Found the problem. This will be fixed in the next VIPM release. [case 10553] Custom Category Palette - "If Newer" Logic Does Not Work Correctly Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.