Skill code to disable all callbacks

Hi,

What do you mean with "all callbacks"? The term generally  callback refers to any Skill code that is triggered by an event as opposed to being called explicitly. Do you talk about CDF callbacks or callbacks in a GUI or what exactly? Disabling literally all callbacks will render your virtuoso session useless.

Max

I want to actually disable the callback controlling the width and length of a device. For example, device range is enforced by a callback so a user cant enter any value outside the range . I want to disable this property temporarily so i can enter values outside the allowed range. 

Given a pmos with w = [ 2 -9 ],  I want to enter a value of 1.

The callback currently doesn't allow that, so I want to bypass it and enter any value

Ok that sounds like a CDF callback. You don't need Skill to delete these. You may edit them in the CDF editor. In the CIW goto

Tools - CDF - Edit...

then pick library and cell from the combo boxes, locate the parameter in question and there you may modify the callback to your hearts content.

Max

Yes, it is a cdf callback scenario, can I do this with skill because I am running in virtuoso no graph mode, so I dont have access to the GUI

Yes, it is a cdf callback scenario, can I do this with skill because I am running in virtuoso no graph mode, so I dont have access to the GUI

This code will do what you want:

/********************************************************************
*                                                                   *
*               CCFresetCallback(lib cell paramName)                *
*                                                                   *
*      Resets the callback in the effective CDF to blank. Does      *
* so by creating user CDF as needed, copying the parameter from the *
*                 base CDF, and resetting it there.                 *
*                                                                   *
********************************************************************/

procedure(CCFresetCallback(lib cell paramName)
  let((ddId cdf userCdf param userParam)
    ddId=ddGetObj(lib cell)
    userCdf=cdfGetUserCellCDF(ddId) || cdfCreateUserCellCDF(ddId)
    userParam=cdfFindParamByName(userCdf paramName) 
    unless(userParam
      cdf=cdfGetBaseCellCDF(ddId)
      param=cdfFindParamByName(cdf paramName) 
      userParam=cdfCopyParam(userCdf param)
    )
    userParam->callback=""
    t
  )
)

Regards,

Andrew

Andrew,

Thanks for this code!
What I don't understand though is why the CDF callbacks get triggered in nograph mode in the first place. I always figured CDF callbacks were form callbacks and in such do require a graphic environment.

Max

Max,

That's a very good point, and one I overlooked.

One possibility is that a replay file is being used which is still interacting with the form, and another is that a generic function (such as abInvokeCdfCallbacks or CCSinvokeCdfCallbacks is being used to trigger the callbacks after a database change; however, if it was that then they have the ability to omit calling specified callbacks anyway, so I assume that can't be it).

We'll need Genas to explain...

Andrew.