• 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. pcell conditional include default overrides any selecti...

Stats

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

pcell conditional include default overrides any selection

gkaatz
gkaatz over 14 years ago
When I instantiate a pcell created with the pcell tool, the checkbox on the Create Instance form or Edit Instance Properties has no effect. The default state of the conditional include is shown. It used to work but with various edits has stopped doing so.
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Little hard to follow, but my guess is that you have a CDF parameter defined and the CDF default is different from the pcell default for this parameter. If you've done that (not a wise idea), then what can happen is that if you instantiate the component where the value on the form matches the CDF default, it omits the property on the instance, and hence the pcell gets the pcell default. If  you have a value which is different from the CDF default, it stores the property on the instance - but since that's the same as the pcell default, you still get the pcell default.

    If you really must have the CDF default different from the pcell default, use storeDefault=yes on that CDF parameter. But it's really best to ensure that the CDF default values match the pcell default values.

    This however is a bit of a guess as to what your problem is - the info supplied above is a big confusing.

    Regards,

    Andrew.

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

    Little hard to follow, but my guess is that you have a CDF parameter defined and the CDF default is different from the pcell default for this parameter. If you've done that (not a wise idea), then what can happen is that if you instantiate the component where the value on the form matches the CDF default, it omits the property on the instance, and hence the pcell gets the pcell default. If  you have a value which is different from the CDF default, it stores the property on the instance - but since that's the same as the pcell default, you still get the pcell default.

    If you really must have the CDF default different from the pcell default, use storeDefault=yes on that CDF parameter. But it's really best to ensure that the CDF default values match the pcell default values.

    This however is a bit of a guess as to what your problem is - the info supplied above is a big confusing.

    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