dbCreateParamInst didn't update graphically in layout

Hi Tony,

I assume you talk about CDF params aren't you? These are form callback that are triggered though the 'Create Instance' and the 'Edit properties' form only.There is a solution available how to trigger the callbacks programmatically in SKILL: Article 11018344: How to call CDF callbacks procedurally from SKILL

To place an instance of a pCell you should always use dbCreateParamInst() or dbCreateParamInstByMasterName() so as you can define the pCell params. The function dbCreateInst is for fixed cell instances only.

regards
Max

hi Max,

I know I can do a callback after I instantiate the pCell.

What is the purpose to define the pCell params if it didn't instantiate with the right value. So define all the parameter during the instantiation become useless.

Tony

Hi Tony,

The pCell params instantiate the way it is implemented it in the pcDefinePcell() function. A pCell doesn't know anything about CDF parameters! What you see in the 'Create instance' form when you place  an instance of a cell that has CDF parameters is in fact the CDF parameters and not the pcell params - it just looks like it was pcell params if the CDF's have the same names like the CDF params. As soon as you overwrite a  CDF param's default value in the 'Create Instance form' that non default value goes as a user defined property to the instance where the pcell code picks it up to compute the submaster. This is actually  the trick why implementing pcell parameters as CDF's does work. But it works only when you place the instance graphically and not in terms of a SKILL command.

So to come back to your question - the purpose to define pcell parameters during the instantiation is to pass those values to the SKILL code that computes he pcell. A CDF callback just intercepts these values before they get attached to the instance - but again that doesn't work in SKILL.

So you must programmatically call the CDF callbacks - no way to get around this.

Max

Thanks Max

Thanks Max