• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. change default GUI callback

Stats

  • Locked Locked
  • Replies 17
  • Subscribers 143
  • Views 20876
  • 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
Leonid Y over 13 years ago

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..

  • Cancel
Parents
  • dmay
    dmay over 13 years ago

    What if you wrap it with a hiRegTimer call to update the deltas right after the form comes up? You would setup your bindkey for placing an instance like this:

    hiRegTimer("myInstCallback()" 1) leHiCreateInst()

    This would initiate your callback one tenth of a second after the form comes up.

    Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dmay
    dmay over 13 years ago

    What if you wrap it with a hiRegTimer call to update the deltas right after the form comes up? You would setup your bindkey for placing an instance like this:

    hiRegTimer("myInstCallback()" 1) leHiCreateInst()

    This would initiate your callback one tenth of a second after the form comes up.

    Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information