• 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. Descending into a cell - skill function

Stats

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

Descending into a cell - skill function

swdesigner
swdesigner over 14 years ago

I currently bind my key to call schHiDescend, and work on the form.

 

Is there a way to bypass the form and call a function with the name of an instance in the current cellview to descend into it?

 

Thanks

  • Cancel
Parents
  • swdesigner
    swdesigner over 14 years ago

    Hello Andrew,

             This still doesn't do it. I think what I need already exists.. but I don't know how to get my hands on it.. Let me explain..

     The code you provided gives me the view being used if I'm viewing a config. If not, pathVector doesn't exist. In that case what do I do?

    However, when I use the descend function (default bindkey is 'e'), Cadence already knows what order to give me the views in... if it's a config, it puts the view being used first in the drop-down menu for view.. If it's not a config, and a schematic view exists, it gives me that on top.

    So, the work is already done. How can I get "that" view (that Cadence puts at the top of the list when using the descend dialog) without using the form, through skill.

    Why do I want to bypass the form?

    Because there is a bug that causes a remnant of that form to remain after bindkey based interaction... some of the time.. and it's an annoyance...

    Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • swdesigner
    swdesigner over 14 years ago

    Hello Andrew,

             This still doesn't do it. I think what I need already exists.. but I don't know how to get my hands on it.. Let me explain..

     The code you provided gives me the view being used if I'm viewing a config. If not, pathVector doesn't exist. In that case what do I do?

    However, when I use the descend function (default bindkey is 'e'), Cadence already knows what order to give me the views in... if it's a config, it puts the view being used first in the drop-down menu for view.. If it's not a config, and a schematic view exists, it gives me that on top.

    So, the work is already done. How can I get "that" view (that Cadence puts at the top of the list when using the descend dialog) without using the form, through skill.

    Why do I want to bypass the form?

    Because there is a bug that causes a remnant of that form to remain after bindkey based interaction... some of the time.. and it's an annoyance...

    Thanks!

    • 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