• 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 134
  • Views 38007
  • 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 15 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,

    I will try to answer each of your questions.

    1) Yes, the benefit of modifying the list "in place" is that everything else remains as it was and should have the default behaviour.

    2) Again, yes, typically your utility functions would be defined in a file that is read by the .cdsinit startup SKILL file (or the function could be defined directly in the .cdsinit file, but generally it is cleaner to load these files).

    3) ?? Eh?  Start the session, test it.  For debugging purposes you might be able to add a printf statement at the end of the file to say that the something.menus file was loaded, you should see it in the CIW.  If you are modifying existing menus without adding or removing anything else then the menu may appear to look the same; perhaps this is your question?  Through SKILL you could check what the menu item callback was...

    4)  Sorry, I have not customized the ADE menus, so I will leave this to Andrew or someone else to reply to.

    5) Did you read the <instDir>/tools/dfII/etc/tools/menus/simui.menus file?  I believe it mentions a function sevAddMenuItemLists() that you might be able to use.  Again, I have not played with customizing the ADE menus, so someone else may be able to add some value here.

    Regards,

    Lawrence.

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

    Hi Zfeng,

    I will try to answer each of your questions.

    1) Yes, the benefit of modifying the list "in place" is that everything else remains as it was and should have the default behaviour.

    2) Again, yes, typically your utility functions would be defined in a file that is read by the .cdsinit startup SKILL file (or the function could be defined directly in the .cdsinit file, but generally it is cleaner to load these files).

    3) ?? Eh?  Start the session, test it.  For debugging purposes you might be able to add a printf statement at the end of the file to say that the something.menus file was loaded, you should see it in the CIW.  If you are modifying existing menus without adding or removing anything else then the menu may appear to look the same; perhaps this is your question?  Through SKILL you could check what the menu item callback was...

    4)  Sorry, I have not customized the ADE menus, so I will leave this to Andrew or someone else to reply to.

    5) Did you read the <instDir>/tools/dfII/etc/tools/menus/simui.menus file?  I believe it mentions a function sevAddMenuItemLists() that you might be able to use.  Again, I have not played with customizing the ADE menus, so someone else may be able to add some value here.

    Regards,

    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