Triggering callbacks

Hi Naveen,

It's hard to know without seeing the specific case, but you might need to tell it to call the callInitProc too - sometimes this has to be done for the callbacks to work. You can do that by calling:

CCSinvokeCdfCallbacks(geGetEditCellView() ?callInitProc t)

The other possibility is that that callback is referring to cdfgForm and looking at the cellName (say) - this is dubious practice, but it does happen sometimes. In that case, try adding ?addFormFields t to the arg list.

If neither work, I suggest you contact customer support. You'll need to provide info on the PDK you're using. If the AE handling the service request isn't sure, they can always contact me (as I wrote the code) for help - but we'd need enough data to reproduce the problem.

Regards,

Andrew.

Hi Andrew,

Is there any remote chance that it wouldn't work if I run it on the top-level hierarchy, which doesn't have any individual instances placed (only blocks)?

The reason behind this conclusion is: I copied the top-level schematic (with all the hierarchy) into a new library and ran "CCSCdfCallbackEntireLib.il". It worked (sort of)!!! I still got the same error messages (seen from the icfb window) when it was running on the top-level schematic but was able to successfully reset few other attributes on other schematic cellviews.

I really appreciate your help (always) !!!

Thanks,

Naveen

Naveen,

If you run on the top level block, it's only going to call the callbacks for the instances placed - so if there's a failing there, it's because of any CDF callbacks on those devices. 

The errors are probably coming as a consequence of the callbacks themselves. Seeing the data is probably the only way to debug this - but you could try typing:

_stacktrace=50
tracelength=50
tracelevel=50

and triggering the callbacks and seeing if the additional information makes it any clearer?

Andrew.