• 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. Hierarchy Editor: Is it possible to add buttons to toolbar...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 142
  • Views 15418
  • 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

Hierarchy Editor: Is it possible to add buttons to toolbar?

ivick
ivick over 5 years ago

Hi Adrew,

Is it possible to add items to the Hierarchy Editor (config file) tool bar? Not even I can see that option in the Toolbar Manager (Virtuoso -> Options -> Toolbars) in order to add it manually.

Thanks,

Ivick

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Ivick, I split this from the original post because it was a) on the end of a 5 year old thread, and b) only had a loose connection with a question about adding buttons to an ADE toolbar. This will make it easier to find for others.

    There's a trigger (since IC618/ICADVM181) which allows you to register a function which is called when the hierarchy editor is opened, and this can be used to either add something to the existing toolbar, or add your own toolbars. It's not done using the Toolbar manager, since that's for "DE" (Design Editor) windows, and HED is not one of those. Here's how to add a new item to the existing toolbar:

    procedure(CCFaddItemToHEDToolbar(win)
      let((toolbar comboItem)
        toolbar=car(hiGetWindowToolbars(win))
        comboItem=hiCreateToolbarComboBox(
          ?name 'comboItem
          ?value "DesignA"
          ?items list( "DesignA" "DesignB" "DesignC" )
          ?editable t 
        )
        when(toolbar
          hiAddToolbarItem(toolbar comboItem)
        )
      )
    )
    
    ; This registration function exists from IC618/ICADVM181 onwards
    hedRegUICustomFunc('CCFaddItemToHEDToolbar)

    Here's how to add a complete new toolbar:

    procedure(CCFcreateToolbarForHED()
      let((comboItem)
        comboItem=hiCreateToolbarComboBox(
          ?name 'comboItem
          ?value "DesignA"
          ?items list( "DesignA" "DesignB" "DesignC" )
          ?editable t 
        )
        CCFHEDtoolbar=hiCreateToolbar(
          ?name 'CCFHEDtoolbar 
          ?title "My Designs" 
          ?items list(comboItem ) 
        )
      )
    )
    
    procedure(CCFaddToolbarToHED(win)
      unless(boundp('CCFHEDtoolbar)
        CCFcreateToolbarForHED()
      )
      hiPlaceToolbar(win CCFHEDtoolbar)
    )
    
    ; This registration function exists from IC618/ICADVM181 onwards
    hedRegUICustomFunc('CCFaddToolbarToHED)

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ivick
    ivick over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks a lot for your reply, unfortunately I am not able to test it because my IC version says *Error* eval: undefined function - hedRegUICustomFunc. Eventually I think I will be upgraded and I will test it.

    In the meantime I would like to ask you the following in order to find a way to add a custom task to the HED:

    1. Is it possible to add a custom menu to HED  by using eRegUserTriggers()?  if so what is the t_viewType value for HED.

    2. Is it possible to add a custom button to the "Top Cell section"? 

    Thanks and regards,

    Ivick

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to ivick

    Ivick,

    1. deRegUserTriggers doesn't work because the hierarchy editor is not a design editor window. That's precisely why we added a trigger function specifically to do HED-specific initialisation/customisation.
    2. No, you can't do that. The docked assistant in the windows is not a SKILL-generated form and so you cannot customise it.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ivick
    ivick over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for the clarification. Now I have one more question that maybe is related with your answer in 1 since I am not able to see any field or property linked when I apply   hiGetCurrentWindow() over an opened config file (HED).

    How can I access to data such libName, cellName and viewName of a manually opened config file?

    btw. By now I have managed to have such information by using ddsGetLibManLCV() and storing the data of the latest opened config file, however if I have more than one opened config file I lost the data of any  config file previously opened.

    Ivick.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to ivick

    Hi Ivick,

    Not really. There's an enhancement CCR I filed a while back, 972584, asking for precisely this. At the moment there's only a private function to do this. I suggest  you contact customer support and ask for a duplicate request to be filed (referencing the CCR number I stated).

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ivick
    ivick over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    I had the hope that something like "putprop(hiGetCurrentWindow() ddsGetLib() 'prop_name)" could work. I will contact to customer support to duplicate the CCR you provided.

    Thanks and regards,

    Ivick.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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