When LabVIEW Class Mutation History builds in your project, the LV Class Library becomes larger and the time to open the class private data becomes longer. This may be obvious if the time exceeds 2 or 3 minutes. How can you determine when it is a problem and needs to be cleared?
There has never been a utility to measure Class Mutation History by the time it takes to open the class. Property Inspector can not only measure this time, a simple set of macros can iterate through all the classes in multiple projects automatically. This mutation can only be measured once after the project is opened because it records the time to parse the class history into memory. Once the class is in memory the time will always be zero.
Property Inspector 5.1 has built-in function to measure the count, time and size of the class mutation history and write it to a log file. The classes are automatically sorted with the highest count first. Call this macro from another macro to open and close the project by path using a parameter. Call that macro from another macro with the project paths.
Check Mutation History.pi5
Settings Object Types Class
Search Type Equals LVClass
Select All
PI Log C:\Temp\Mutations\Mutation Log %DATE.txt
Log Show Mutation History for %NAME
PI Mutation
PI Log
