Stats

  • Locked Locked
  • Replies 17
  • Subscribers 143
  • Views 20875
  • 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

change default GUI callback

Leonid Y

Hello guys,

 I am a bit new to skill programming. I would like to change default behaviour of a standard form. Basically I would like one field to change its value when another field is modified in a default form. To be more specific, I want some exact values to be set in "Create Instance"  dialog for the "Delta X", "Delta Y" fields when a particular Lib Cell View is chosen.

I have found out that the form is bound to  the leCreateInstForm structure and it , in turns, has the fields: libName cellName viewName instName and so on; Each one has a list of properties including more interesting for me:

 _focusInCallback

 _modifyCallback

_callback

The values of first two properties are empty "" and the last one is set to

 "leInstCellNameCB(leCreateInstForm~>cellName~>value)"

which I suppose default skill routine which checks for cellview existence  in Library Manager and something else. I guess it is exactly where the things happen.

Till this moment everything seems to be clear, but when I replace  the default routine with my own one , which does just perfect when it is fed to CIW , it not only does not do what I expect but the whole mechanism seems to get broken till I restart icfb.

So, my questions :

- is it possible in general to change default behaviour in my case? some straight ways or tricky ones.

- what does the underscore  sign in the beginning of _callback property mean? There must be some special meaning..

Parents
  • Leonid Y

     I continued my investigation. I played with whole form callback defined it according to Andrew's advice , but still do not see any effect even for this case. Simply no changes. Should I call some function which reloads something in order to apply a change?

    Also , returning back to assigning a function to a form field - is it OK just to use "=" operator? because the  hiChangeFormCallback operates at a form level, i.e. it does not accept a field (e.g. leCreateInstForm->cellName) as a parameter.

    Please help, I have no idea where to find an answer. The only reference guide I know is skuiref which seems not be too willing to give some info about adjusting built-in functionality. And I am stuck in the very beginning.

Reply
  • Leonid Y

     I continued my investigation. I played with whole form callback defined it according to Andrew's advice , but still do not see any effect even for this case. Simply no changes. Should I call some function which reloads something in order to apply a change?

    Also , returning back to assigning a function to a form field - is it OK just to use "=" operator? because the  hiChangeFormCallback operates at a form level, i.e. it does not accept a field (e.g. leCreateInstForm->cellName) as a parameter.

    Please help, I have no idea where to find an answer. The only reference guide I know is skuiref which seems not be too willing to give some info about adjusting built-in functionality. And I am stuck in the very beginning.

Children
No Data

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.