• 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. Smart snapping API / Edit-in-place question

Stats

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

Smart snapping API / Edit-in-place question

dmay
dmay over 9 years ago

Has Cadence provided a Skill API to do smart snapping or highlighting in 6.1.6? The Ruler, Quick Align and Edit-in-place commands all have some great shape highlighting features that are pretty efficient. I'd prefer not to write my own if we can use a built-in Skill command.

My next question is if there is a way to turn off the error message for editing-in-place pcells? For years we have had our own edit-in-place Skill procedure that uses leEditInPlace(window instPath) to perform the eip. Our designs use a lot of pcells, and this code will actually eip into the pcell without an error message. Our Skill would then ascend to one level above the pcell automatically. This makes it very easy for a designer to get to the level of hierarchy where the edit needs to be performed.

In 6.1.6, the leHiEditInPlace command has a nice feature that dynamically highlights the shapes under the cursor to help you pick where you want to descend. The problem is that if you click on a pcell, you get the pop-up error message that won't let you descend into a pcell, and no hierarchy is traversed at all. If I can't turn off this warning, then I am forced to write this dynamically highlighting myself.

What I find interesting is that leHiEditInPlace will not highlight shapes inside a pcell (seems consistent based on feature that won't let you eip into the pcell), but if my pcell has customVias in it, it will let me descend into the customVia inside the mos pcell. Sounds like a bug, but this at least allows me to ascend back to a level above the mos. If I can just disable the pcell error and descend wherever I want, then I can write a descend wrapper around leHiEditInPlace with built-in highlighting and auto-ascend as needed. If I can't disable the error, then I need to write my own highlighting routine, and continue with our code that builds the inst path and calls leEditInPlace.

Derek

  • Cancel
Parents
  • theopaone
    theopaone over 9 years ago

    I haven't tested this as I have no access to Virtuoso at this time but here is an idea:

    1. Find the element using dbGetTrueOverlaps. This returns a list of the hierarchy down to the element ID itself.

    2. Step through the list using geEditInPlace. Check the master of the instance before each EIP,  if it is a pcell, stop before entering the pcell.

    It may have performance issues.

    Ted

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • theopaone
    theopaone over 9 years ago

    I haven't tested this as I have no access to Virtuoso at this time but here is an idea:

    1. Find the element using dbGetTrueOverlaps. This returns a list of the hierarchy down to the element ID itself.

    2. Step through the list using geEditInPlace. Check the master of the instance before each EIP,  if it is a pcell, stop before entering the pcell.

    It may have performance issues.

    Ted

    • 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