Stats

  • Locked Locked
  • Replies 5
  • Subscribers 144
  • Views 16296
  • 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

Custom Layout toolbar menu

skillforpcells

Hello All,

I want to have customized Layout tool bars. but every time I set the tool bars in Layout and reopen it, the tool bars initially set are gone. I have to set my configuration every time and this is time consuming. I checked the CIW and found that each time I open the tool bars the command are different, for example If I open the search tool bar, I get

hiShowToolbar(swindow(10)->hiToolbars->leSearchToolbar_10)

next time

hiShowToolbar(swindow(11)->hiToolbars->leSearchToolbar_11)

How to deal with this and is there a posiblity that I can make configurations in a file and place them as layEdit.menus under menus ?

  • You are asking two different questions, the first is how to have a custom toolbar inserted in the window when a mask layout cellView is opened. This is done by a user trigger which is evaluated once the window is opened. Here it is used to add a menu to the window. You could do the same with a tool bar.

       printf( "Setting menu trigger\n" )
        unless( member( 'MyMenuInstallMenuTrigger
                 deGetAppInfo( "maskLayout" )->userPostInstallTrigList )
            deRegUserTriggers( "maskLayout" nil nil 'MyMenuInstallMenuTrigger )
            printf("Trigger installed.\n")
        ) ; unless

    The second question is about displaying SKILL custom menus (note the menu number attached to the toolbar symbol), the configuration can be saved and loaded by the user or using a trigger as above.

    Ted

  • I was able to find the solution and is discussed in another form http://community.cadence.com/cadence_technology_forums/f/38/p/25757/1321965#1321965
  • Thanks theopaone, I was also able find a workable solution in another forum.

  • Ted,

    I should point out that it is not good practice to use a user post install trigger to insert banner menus. This historically has caused problems when people do so because it can interfere with the normal banner menu installation process (which would be done using menu triggers - i.e. a userMenuTrigger). That's the purpose of the third argument to deRegUserTriggers rather than the fourth - that trigger should return a list of pulldown menus to insert.

    For toolbars, you can do this best with toolbar files - this allows you to determine custom toolbars and you can have your toolbar files inherit the standard toolbars - and then  you can set up a workspace which enables your custom toolbar by default. This way it will show up in the list of toolbars in the WIndows->Toolbars menu too. You can do it with a post install trigger, but it is a better fit for the design editor system if you do it via toolbar files.

    Regards,

    Andrew.

  • My code is the result of an evolution from an old example, the code existed to create and insert the menus so it was used.

    I will now change my methodology to separate the creation and insertion phases of the menus, the create function would return the list needed for the menu trigger, the generic menu insertion function would insert the return value into the menu list. The insertion method function would only be called for testing.

    I have not worked with Workspaces much so it is good to find the save/restore/default solution.

    Old dogs can learn new tricks.

    Ted

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.