Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 15749
  • 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

Drop-down menu disappears from schematic window, moving into layout window when VXL is launched

DannyR

Hello,

A custom Drop Down menu, skill based, for Virtuoso is showing OK when launching Layout or Schematic windows individually. When VXL is launched from schematic window the Drop Down menu disappears from the schematics window and moves to  the layout window. Upon loading Virtuoso I am loading Triggers.il file as shown below.

Any tip why will be greatly apperciated...


Thanks,

Danny

-----------------------------------------------------------------------------


; LAYOUT Triggers
 procedure(DRSetups(args)

  leSetObjectSelectable("Blockages" nil)
  leSetObjectVisible("Blockages" nil)

  leSetObjectSelectable("Boundaries" nil)
  leSetObjectVisible("Boundaries" nil)

;  leSetObjectSelectable("ruler" nil)
;  leSetObjectVisible("ruler" nil)

;  leSetObjectSelectable("Markers" nil)
;  leSetObjectVisible("Markers" nil)

  ; Turn on all Valid Layer
  leSetAllLayerValid(t)

  ; CAD Utilities
  ; Layout
  UtilitiesMenu()

 ); procedure


;  Schematic Triggers
procedure(schSetups(args)

  ; CAD Utilities
  schUtilitiesMenu()

 ); procedure


;; create a user postinstall trigger that automatically setup

deRegUserTriggers("maskLayout" nil nil 'DRSetups)
deRegUserTriggers("maskLayoutXL" nil nil 'DRSetups)
deRegUserTriggers("maskLayoutGXL" nil nil 'DRSetups)
deRegUserTriggers("schematic" nil nil 'schSetups)
deRegUserTriggers("schematicXL" nil nil 'schSetups)

;;; VXL 6.1.6
------------------------------------------------------------------------------------------

Parents

  • Danny,

    I've worked out the problem. First of all, it seems that registering the trigger for Schematic XL isn't strictly necessary - it calls the Schematic L trigger anyway and retrieves the menus for that. So the function to retrieve the schematic menus gets called twice.

    Now this in itself isn't a major problem, unless you always redefine the menu. In my case I had code around it to prevent it unnecessarily recreating the menu if it had already been created - and that stops the problem from occurring too. So changing your code to:

    procedure( schUtilitiesMenu(args)

    ; changed to only create it the first time
    unless(boundp('SCHutilitiesPulldownMenu)
    ; If pull down menu does not exist, create it

    ; PullDown menu Creation
    ;-----------------------

    SCHutilMenuItemOne=hiCreateMenuItem(
     ?name  'SCHutilMenuItemOne
     ?itemText "NET Information"
     ?callback "schSpecificNetApp()"
     )


    SCHutilMenuItemTwo=hiCreateMenuItem(
            ?name           'SCHutilMenuItemTwo
            ?itemText       "NET Hierarchical Information"
            ?callback       "schNetApp()"
            )

    SCHutilMenuItemThree=hiCreateMenuItem(
            ?name           'SCHutilMenuItemThree
            ?itemText       "Hierarchy Tree"
            ?callback       "CCShiSchTree()"
            )

    hiCreatePulldownMenu(
     'SCHutilitiesPulldownMenu
     "Schematic Utilities"
                  list(
                     SCHutilMenuItemOne
                     SCHutilMenuItemTwo
                     SCHutilMenuItemThree
                     
              )
           )
    )

    list(SCHutilitiesPulldownMenu)

    ) ; End of procedure( schUtilitiesMenu()

    This should fix it too.

    Andrew.

Reply

  • Danny,

    I've worked out the problem. First of all, it seems that registering the trigger for Schematic XL isn't strictly necessary - it calls the Schematic L trigger anyway and retrieves the menus for that. So the function to retrieve the schematic menus gets called twice.

    Now this in itself isn't a major problem, unless you always redefine the menu. In my case I had code around it to prevent it unnecessarily recreating the menu if it had already been created - and that stops the problem from occurring too. So changing your code to:

    procedure( schUtilitiesMenu(args)

    ; changed to only create it the first time
    unless(boundp('SCHutilitiesPulldownMenu)
    ; If pull down menu does not exist, create it

    ; PullDown menu Creation
    ;-----------------------

    SCHutilMenuItemOne=hiCreateMenuItem(
     ?name  'SCHutilMenuItemOne
     ?itemText "NET Information"
     ?callback "schSpecificNetApp()"
     )


    SCHutilMenuItemTwo=hiCreateMenuItem(
            ?name           'SCHutilMenuItemTwo
            ?itemText       "NET Hierarchical Information"
            ?callback       "schNetApp()"
            )

    SCHutilMenuItemThree=hiCreateMenuItem(
            ?name           'SCHutilMenuItemThree
            ?itemText       "Hierarchy Tree"
            ?callback       "CCShiSchTree()"
            )

    hiCreatePulldownMenu(
     'SCHutilitiesPulldownMenu
     "Schematic Utilities"
                  list(
                     SCHutilMenuItemOne
                     SCHutilMenuItemTwo
                     SCHutilMenuItemThree
                     
              )
           )
    )

    list(SCHutilitiesPulldownMenu)

    ) ; End of procedure( schUtilitiesMenu()

    This should fix it too.

    Andrew.

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.