• 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. Allegro X PCB Editor
  3. Adding a new menu item to Allegro PCB Editor

Stats

  • Replies 26
  • Subscribers 164
  • Views 27165
  • Members are here 0
More Content

Adding a new menu item to Allegro PCB Editor

chads108
chads108 over 13 years ago

 I want to add, or really append, a new menu item to the Allgro PCB Editor menu.  What is the easiest way to handle this without having to modify the installed menu?  Maybe someone has an example that I could follow?

  • Sign in to reply
  • Cancel
Parents
  • fxffxf
    fxffxf over 13 years ago

    For design types (e.g brd, mcm etc) see the doc for the function

        axlDesignType

    For just dra vs everything else

         axlIsSymbolEditor

    For either of these you can use axlUIMenuRegister since you need to perform the test at menu load time. For these you need to use the  axlTriggerSet with a registered callback function (see example file below).

    I don't believe their is a easy way of telling the difference between product levels except using some of the dynamic underscore env variables (do a "set" cmd and look at the end of the list generated). Some are documented in allegro.men but others you will need to reverse engineer.

    To differentiate between SI and PCB you allegro t menu loading via the axlTriggerSet('menu ...) then you can look at the menu name in the callbacks 1st argument.Allegro's menu is "allegro" while SI is "spectraquest". You can look the menu example file in <cdsroot>/share/pcb/examples/skill/ui/menu.il.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • fxffxf
    fxffxf over 13 years ago

    For design types (e.g brd, mcm etc) see the doc for the function

        axlDesignType

    For just dra vs everything else

         axlIsSymbolEditor

    For either of these you can use axlUIMenuRegister since you need to perform the test at menu load time. For these you need to use the  axlTriggerSet with a registered callback function (see example file below).

    I don't believe their is a easy way of telling the difference between product levels except using some of the dynamic underscore env variables (do a "set" cmd and look at the end of the list generated). Some are documented in allegro.men but others you will need to reverse engineer.

    To differentiate between SI and PCB you allegro t menu loading via the axlTriggerSet('menu ...) then you can look at the menu name in the callbacks 1st argument.Allegro's menu is "allegro" while SI is "spectraquest". You can look the menu example file in <cdsroot>/share/pcb/examples/skill/ui/menu.il.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
Cadence Guidelines

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