• 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. Nesting commands in Virtuoso Layout Suite L User Guide

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14259
  • 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

Nesting commands in Virtuoso Layout Suite L User Guide

BaaB
BaaB over 9 years ago

This is a description about nesting commands in Virtuoso Layout Suite L User Guide:

You can pause before completing one command to perform a second command. This is called nesting a command. For example, if you move an object and then zoom out, the zoom command would be nested, allowing you to use another command such as moving another object.


I don't understand how it works. Could you explain more? In this case, we are moving an object then zoom out and the zoom command is nested.

How can I move another object without escape the current command? I tried the example above but I couldn't move another object as the description.

What does it mean to set the nest limit to 2 or 3?

Thank you.

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

    The principle behind nesting is that you can start one command, then when in the middle of that command, start another, then start another and so on; as you finish each command it pops back out to complete the previous command. 

    Mostly this is used to allow you to do things like start an editing command (like copy, move, stretch etc) and then do a zoom whilst within that. For example, I could start move, then hit z to zoom and before I zoom I hit Tab to do a Pan (or pick the menu). I finish the pan by clicking on a new location, then I am prompted to finish the zoom, and then it goes back to the move.

    Some of the flexibility has been removed in order to get better consistency and to reduce confusion. Some of the editing commands reset the nesting stack - so when you start a copy or a move, it effectively starts the stack from scratch again - so any commands you were doing before are replaced by the new command. In the past in older versions, you used to be able to get in a bit of a mess with the nest stack and sometimes the stack wouldn't get reset so after some time you'd have to increase the nesting stack to get the tools to behave properly. I've not seen that problem for years though.

    So I'd say nowadays there's really no need to touch the nest limit (in Options->User Preferences in the CIW) because the default is pretty much always sufficient.

    Regards,

    Andrew

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

    The principle behind nesting is that you can start one command, then when in the middle of that command, start another, then start another and so on; as you finish each command it pops back out to complete the previous command. 

    Mostly this is used to allow you to do things like start an editing command (like copy, move, stretch etc) and then do a zoom whilst within that. For example, I could start move, then hit z to zoom and before I zoom I hit Tab to do a Pan (or pick the menu). I finish the pan by clicking on a new location, then I am prompted to finish the zoom, and then it goes back to the move.

    Some of the flexibility has been removed in order to get better consistency and to reduce confusion. Some of the editing commands reset the nesting stack - so when you start a copy or a move, it effectively starts the stack from scratch again - so any commands you were doing before are replaced by the new command. In the past in older versions, you used to be able to get in a bit of a mess with the nest stack and sometimes the stack wouldn't get reset so after some time you'd have to increase the nesting stack to get the tools to behave properly. I've not seen that problem for years though.

    So I'd say nowadays there's really no need to touch the nest limit (in Options->User Preferences in the CIW) because the default is pretty much always sufficient.

    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