• 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. dump all the layer from Palette Assistant window in case...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 14246
  • 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

dump all the layer from Palette Assistant window in case of no LSW layer definitions in the specified technology database

zssfred
zssfred over 8 years ago

Any ideas from skill?

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Fred,

    The callbacks for all form fields are simply a SKILL expression that is evaluated whenever the form value changes (most of them when the focus moves away from that field). The idea is that the function you call then can react to the change the user has made to the field value, and either check the value they've specified (and do something with that) or compute the value of another field based on the current value of the field.

    So it would get called whenever you picked a different value for the layer-purpose in this field.

    I'm not sure it would be very useful to offer a complete list of layer-purposes in the choices, and then have the callback check to see if it's valid; it would probably be better just to provide the list of valid layer purposes as choices and then there's no need to check that in a callback. The use model would be a bit strange otherwise.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Fred,

    The callbacks for all form fields are simply a SKILL expression that is evaluated whenever the form value changes (most of them when the focus moves away from that field). The idea is that the function you call then can react to the change the user has made to the field value, and either check the value they've specified (and do something with that) or compute the value of another field based on the current value of the field.

    So it would get called whenever you picked a different value for the layer-purpose in this field.

    I'm not sure it would be very useful to offer a complete list of layer-purposes in the choices, and then have the callback check to see if it's valid; it would probably be better just to provide the list of valid layer purposes as choices and then there's no need to check that in a callback. The use model would be a bit strange otherwise.

    Regards,

    Andrew

    • 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