How to make all schematics in the library not editable using SKILL ?

Hi Marben

Maybe it would be good for you to first provide some info on the following:

a. Are you using any version management software (e.g. DesignSync, ICmanage, etc)? If yes, do you mean that the layout engineer checked out the schematic, edited it and then check in the schematic?

b. Do the schematic and layout engineers share the same linux account?


Best regards
Quek

Hi Quek,

a. Are you using any version management software (e.g. DesignSync, ICmanage, etc)? If yes, do you mean that the layout engineer checked out the schematic, edited it and then check in the schematic?
Answer : No, I'm not using any version management software (e.g. DesignSync, ICmanage, etc).

b. Do the schematic and layout engineers share the same linux account?
Answer: Yes, the schematic and layout engineers share the same linux account.

Best regards,

Marben

Hi Marben

I have heard about such scenarios. Unfortunately, this cannot be easily resolved because of the account sharing. I think a possible but not so effective implementation can be as follows:

a. All layout engineers must have "setenv layoutDesigner yes" in their .cshrc file

b. Use the following SKILL procedure:

procedure( CCSsetSchAsReadOnly(args)
   let( ()
      when( getShellEnvVar("layoutDesigner")=="yes"
         printf("Setting schematic cell %s to read-only for layout designers\n" args->cellName)
         dbReopen(geGetWindowCellView() "r")
         ; Add more codes to disable "File->Make editable", etc
      ) ;when
   ) ;let
) ;procedure


deRegUserTriggers("schematic" nil nil 'CCSsetSchAsReadOnly)
deRegUserTriggers("schematicXL" nil nil 'CCSsetSchAsReadOnly)

Using separate linux accounts is the best solution. All the best for 2019. : )


Best regards
Quek

Hi Quek,

Thank you very much for your code.

Yes, I think so, using separate linux accounts is the best solution,

and making a backup pf the whole library.

Best regards,

Marben