• 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. SKILL approach to detach labels from pin

Stats

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

SKILL approach to detach labels from pin

SSR
SSR over 2 years ago

I'm looking for a SKILL approach to detach labels from pins.

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

    With the label object, do labelId~>parent=nil - this will detach it.

    Andrew

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

    With the label object, do labelId~>parent=nil - this will detach it.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • SSR
    SSR over 2 years ago in reply to Andrew Beckett

    Thanks Andrew.

    Even though the 'geGetSelSet()~>parent' shows nil, its still attached to a 'dot'.  I'm unable to get the label detached from the dot pin.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to SSR

    I am guessing that the label is not in fact a label in that case, but a textDisplay. If you (say) create a dot pin and have a label attached (and don't have the "Create as Label" checked on the options form for creating the associated label), it will be created as a textDisplay. If you then set the parent on the textDisplay to be nil, then it is actually detached from the pin figure, and so if you move the pin figure the "label" won't move with it. The textDisplay is however still associated with the terminal - because it displays the terminal name.

    However, if you delete the dot pin (and there's only a single pin for a given terminal name), then the terminal gets deleted, and because there's nothing for the textDisplay to be associated with, the textDIsplay goes too. You can see this behaviour more clearly if you create two dot pins with associated textDisplays for the same terminal name. Then set the parent for each textDisplay to nil. If you then delete either dot pin, the two textDisplay objects remain. If you delete the second dot pin, they both are removed - because at that point, the terminal gets cleaned up.

    Try selecting the "label" and doing: geGetSelSet()~>objType and seeing if it reports ("label") or ("textDisplay")

    I can''t think of any other explanation...

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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