Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15668
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Keeping Library colors in Library Manager

GoRangers

Hi,

I noticed IC6.1's new feature to allow you to "ASSIGN libname DISPLAY colorname".   It works, but you have to hand-hack the cds.lib.

 But I'm coding some library utilities which utilize the ccp functions, and I want to retain the colors whenever I copy/rename a library.  All the ASSIGN statements get orphaned whenever I move libraries around via ccp.   How do I keep the ASSIGN statements in lockstep with my ccp operations?    Do I actually have to open the cds.lib file as an ASCII and sed/grep everything with a series of system calls from Skill??  

 Surely someone has hit this before?   When your ASSIGN statements all get orphaned, that's pretty bad.

thanks

 

Parents
  • GoRangers

    No kidding.  I filed a bug (not an enhancement) and it got binned.  An API should not be necessary--if you delete a library, the ASSIGNs should go with it.  If you copy or rename a library, the ASSIGNs should go with it.  The Skill I/O functions work, but as far as I'm concerned that is a bug that it is not default Virtuoso behavior.   Cadence should not be orphaning ASSIGNs in a way that is clearly wrong. 

Reply
  • GoRangers

    No kidding.  I filed a bug (not an enhancement) and it got binned.  An API should not be necessary--if you delete a library, the ASSIGNs should go with it.  If you copy or rename a library, the ASSIGNs should go with it.  The Skill I/O functions work, but as far as I'm concerned that is a bug that it is not default Virtuoso behavior.   Cadence should not be orphaning ASSIGNs in a way that is clearly wrong. 

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.