
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
Svenn, You might want to take a look at an application note I wrote some time ago on dd triggers - I give an example which shows how to implement a simple access-control-list mechanism - you could use a similar technique to disallow edit access to certain libraries. http://sourcelink.cadence.com/docs/files/FFF/199/triggers.html There isn't any special builtin syntax for including a readonly library, but you can get around it with the above. Regards, Andrew. On 27 Nov 2003 05:03:05 -0800, [EMAIL PROTECTED] wrote: >Hi, > >as sole user in a multiproject environment, I often have to change >between designs. So far I do this by exiting and restarting icms >because I have bad experience with cds.lib and changing designs >elsewhere in directory tree which I didn't want to. Making the files >read only is not an option as I change between the designs for editing >fairly often. > >I am looking for a function to say that "in current schematic session, >all files that are included with SOFTINCLUDE are read only, and cannot >be forced write by the make editable button, even if the file is owned >by me." > >It will help me if I can write a skill routine, which inspects the >cds.lib and set the properties based on what it find, no need to >change Cadence Composer .... > >If somebody have some hooks for me to start with, I can go on from >there by myself. -- Andrew Beckett Senior Technical Leader Custom IC Solutions Cadence Design Systems Ltd
| <-- __Chronological__ --> | <-- __Thread__ --> |