Written in front: This tip has only been tested under IC61.
Children's shoes working on projects in the group may encounter such a situation. When you open the Library Manager of Cadence, you find that there are dozens of libs on the left. In addition to the various process libraries provided by the manufacturer, there are also libraries of your own design, and sometimes you have to call other people's libraries. As shown in the picture below: (In order to be lazy, the author just put a few meanings...)
Not only does this default style look unsightly, but it is also a headache to manage. As a siege lion pursuing aesthetics, this is simply unacceptable. In fact, in Cadence, the Library manager has such a function.
Click the view option at the top of the library manager, one of which is Display options:
Then select the Edit button behind Custom library display attributes, and a Display Settings window will pop up. In this window, there is only one Invisible label. Of course, you can also help others set their lib to invisible, but be careful of being killed...
Click the add button to create a new category of your own. Here I enter Techref, which is used to place the process library. Then you can choose the color and icon on the right. Here I set the process library to red and use a mos as the icon, as shown in the following figure:
Then go to the working directory, open the cds.lib file, and enter:
ASSIGN analogLib DISPLAY Techref
ASSIGN basic DISPLAY Techref
ASSIGN functional DISPLAY Techref
… Assign all
you want to be included in the craft library into the category of Techref, and then restart the library manager. See if the current process library has all become red names, and there are icons in front of them.
Some people say that this still looks messy, can it be further classified? Of course.
Let's create a new library called TechLib, and then assign its Display to Techref:
ASSIGN TechLib DISPLAY Techref adds
another line of code:
ASSIGN TechLib COMBINE US_8ths ahdlLib analogLib…
Then refresh it, so you can see that a secondary directory TechLib appears. Does this make it clearer?
Tips: In cds.lib, the define command of creating a new TechLib should be placed before the above two lines of code.
In this way, we can classify different types of lib, does it look a lot cooler~~~