• 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 Design
  3. Cadence Virtuoso try to compile every layout to pcell

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 124
  • Views 5825
  • 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

Cadence Virtuoso try to compile every layout to pcell

mad monster
mad monster over 10 years ago

Virtuoso try to do this during design saving.
But it occur not for all libraries. In what there can be a problem?

  • Cancel
Parents
  • mad monster
    mad monster over 10 years ago
    Hello, Andrew!Thank you for your reply.
    geGetEditCellView() partially helps to resolve my problem (for certain cellViews, not for entire library).
    When I typed geGetEditCellView()~>viewSubType it returned its value (not nil, I forgot value).
    Then I typed geGetEditCellView()~>viewSubType = nil and exited from Virtuoso (with saving).
    In the next time this layout was repaired and there were no Pells properties.
    Good day to you,Yuriy.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • mad monster
    mad monster over 10 years ago
    Hello, Andrew!Thank you for your reply.
    geGetEditCellView() partially helps to resolve my problem (for certain cellViews, not for entire library).
    When I typed geGetEditCellView()~>viewSubType it returned its value (not nil, I forgot value).
    Then I typed geGetEditCellView()~>viewSubType = nil and exited from Virtuoso (with saving).
    In the next time this layout was repaired and there were no Pells properties.
    Good day to you,Yuriy.
    • 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