2 of 2 people found this helpful
Changelog from version 02 to 1.0 (considered final ;-)
- optimized for performance
- more verbose, messages to output window
- checks whether single or multi board design, whether design is open
- error checking when adding property
- nicely commented ;-)
just one suggestion: wouldn't it be useful to call this during Packaging?
Maybe as a checkbox in the Packaging Dialog, (well not sure if the packaging Dialog is hard coded or can be modify via script)
As an FYI there is a Mentor supported script on Supportnet (https://supportnet.mentor.com/portal?do=reference.technote&id=MG544054) that does the same for any property and makes use of the PropThruHier and StopPropThruHier propertes to control the level of traversal.
True, with one difference. The add cluster script does not need a cluster propertyat the block symbol with the (hierarchical) blockname added to it.
So it's less effort to setup and always contains the "correct" value (the block's name)
There are many ways to run this, but each one has it's pros and cons.
Ideally it would be run before forward-annotating to Xpedition.
But when it runs automatically it would then overwrite eventual custom changes the designer did for the cluster property...
... So in the end it's up to the individual designer/sysadmin on how to hook it into their process ;-)