Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 15469
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to trigger the event to use the callback?

loosin

Hi,

  I have a question. I wrote a skill procedure to create res pcell and cdf for instance. when I change the w, l and res value, the callback will be trigger and calculation the correct value and return the value to the property list.

But when I use "q" to show the "Edit Object Properties" in virtuoso schematic,  and change the res "cell Name" to other res type such change rpplus to rnplus, the w, l, res value will directly pass from the rpplus to rnplus, not any change, but part of other parameter such rho and model will change from rpplus to rnplus. Now when I change the w or l value, the callback will be trigger and the res value will return correct value.

 I want to know how to get such change event and make the callback procedure to automatic calculation the res value by the correspond new rho(rnplus) and refresh it, not remain the old rpplus value and need to change the w or l to get correct value by hand.

May anyone help me? Thanks

 

Loosin

  • Loosin,

    You can't. There's the possibility to disable the lib and cell fields on the edit properties form - which is how some people prevent this scenario.

    I would suggest logging a service request on this - there are CCRs requesting some kind of callback on the changing of cells; it's not quite as straightforward as just needing to call the callbacks - you may have property values which are meaningless on the new instance (e.g. default values with storeDefault=yes can mean that you can end up with the wrong model if you're not careful).

    Andrew.

  •  

    Thanks Andrew, I got it. I can't trigger cdf callback by the property change.

     

    Loosin

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.