Change default value of a CDF parameter

Of course. You use:

cdf=cdfGetBaseCellCDF(ddGetObj("testLib" "testCell"))
cdfFindParamByName(cdf "paramName")->defValue=nil

You didn't show what you were actually doing, so it's hard to guess what you did wrong.

Andrew

Some parameters need their default changed, I do:

cdf=cdfGetBaseCellCDF(ddGetObj("testLib" "testCell"))
foreach(parameter cdf~>parameters when(condition parameter~>defValue=nil))

This produces the error.

I noticed in my initial message above I wrote parameter~>value=nil, this should of course be parameter~>defValue=nil

I just tried to use cdfFindParamByName to change the default value, it generates the same error.

I included the details of the specific cdf parameter to give some insight:

(description nil callback "cbProcedure" choices
nil data cdf:0x0x3f3eb110 defValue t
display "deGetEditCellView()->cellViewType == \"maskLayout\"" dontSave nil editable
"deGetEditCellView()->cellViewType == \"maskLayout\"" formField nil id dd:0x396e40b0
name "paramName" paramType "boolean" parseAsCEL
nil parseAsNumber nil prompt "paramName"
units nil storeDefault nil type
"baseCellData" use nil value t
)

Nothing obvious here - I can't see why that would cause it to complain about the effective CDF when you're editing the base CDF.

Can you dump the Base CDF from the Tools->CDF->Edit form (with Base selected) in the CIW and share the resulting file?

It shouldn't make any difference whether you're using cdfFindParamByName or iterating through the ->parameters as you're doing.

Andrew

I'm afraid I can't do that since I'm not sure what kinds of NDA I will be violating with posting this publicly.

I tried changing the default with the edit form, this works. Maybe it's the techno the CDF is originally coming from that gives the issue. I did these kind of changes before with a whole variety of different techno's and flavours and this is the first time it fails. In this case it's an older techno with a buggy CDF already from the fab.

I created a workaround for my application using the CB to have a "secondary default" so for now my problem is solved. If this issue occurs again in another techno I think I'll have to contact customer support for this.

I looked into this a bit further and I found out that I always get this warning when I try to set the default to nil. By coincidence the only thing I did before was to set the defValue of a boolean to t.

So no matter what, when I want to set the defValue of a boolean to nil, it fails. Is there another procedure to set this to nil?

It's a bug. I've reproduced it. I found an old CCR on this: 1683564 (there's an even older one too). As a workaround there's this article:

How to change the defValue of a boolean CDF parameter in SKILL?

Unfortunately the article has a limitation - it doesn't preserve the order of the parameters - it will recreate the boolean parameter at the end of the parameter list. It could be modified to do that, but would complicate matters considerably.

You might want to request a duplicate CCR is filed by contacting customer support.

Regards,

Andrew