• 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. How to create personalized menu in virtuoso layout edit...

Stats

  • Locked Locked
  • Replies 29
  • Subscribers 130
  • Views 34653
  • 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

How to create personalized menu in virtuoso layout editor

AmitBiswas
AmitBiswas over 14 years ago
Hi, I have written few scripts in skill language. I want group all the scripts together into a single menu in virtuoso layout editor. Like in the layout editor window there are several menus at the top containing multiple functions, I want to create my personalized menu in the layout editor window. I also want to put that script in the .cdsinit file, so that when cadence will be started the menus will be loaded automatically in the layout editor window like the other menus. Thanks in advance, Amit
  • Cancel
Parents
  • skillUser
    skillUser over 14 years ago

     Hi Zfeng,

    You can create a "menus" directory in your home directory, or current working directory, for example, and then have an appropriately named <tool>.menus file - this file can be used to reference the default menus file, for example load it in and then modify the structures in place, if you only needed a small alteration from the original.  Some menus are easier to do this way, in my opinion. Here is a brief example of changing the File->Exit item in the CIW menus using this method:


    load(prependInstallPath("etc/tools/menus/ciw.menus"))

    ;; only when the ciwFilePulldown menu exists
    when(pairp(ciwFilePulldown)
    ;; create a local variable to store the Exit item
    let( ((exitItem assoc('ExitItem caddr(ciwFilePulldown))))
    ;; replace the callback on the Exit item to be MYexit()
    ;; if the correct menu structure is found

    when(and(exitItem cddr(exitItem))
    setcar(cddr(exitItem) "MYexit()")
    )
    )
    )

    The file would be called "ciw.menus" and be in the menus directory as mentioned above.  This modifies the menu callback of the existing File -> Exit menu item such that the function "MYexit()" is called instead of the default callback.

    I hope that this is helpful.

    Lawrence.

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

     Hi Zfeng,

    You can create a "menus" directory in your home directory, or current working directory, for example, and then have an appropriately named <tool>.menus file - this file can be used to reference the default menus file, for example load it in and then modify the structures in place, if you only needed a small alteration from the original.  Some menus are easier to do this way, in my opinion. Here is a brief example of changing the File->Exit item in the CIW menus using this method:


    load(prependInstallPath("etc/tools/menus/ciw.menus"))

    ;; only when the ciwFilePulldown menu exists
    when(pairp(ciwFilePulldown)
    ;; create a local variable to store the Exit item
    let( ((exitItem assoc('ExitItem caddr(ciwFilePulldown))))
    ;; replace the callback on the Exit item to be MYexit()
    ;; if the correct menu structure is found

    when(and(exitItem cddr(exitItem))
    setcar(cddr(exitItem) "MYexit()")
    )
    )
    )

    The file would be called "ciw.menus" and be in the menus directory as mentioned above.  This modifies the menu callback of the existing File -> Exit menu item such that the function "MYexit()" is called instead of the default callback.

    I hope that this is helpful.

    Lawrence.

    • 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