• 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. deRegUserTrigger warning message

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 142
  • Views 13754
  • 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

deRegUserTrigger warning message

mctang
mctang over 9 years ago

Hi All,

I created a  skill code which uses deRegUserTriggers. I get the following warning message when I open same layout. Is there an solution for this issue ?

*WARNING* __deMakeBannerMenus ("maskLayoutXL"), duplicate menu(s) removed
*WARNING* __deMakeBannerMenus ("maskLayoutXL"), duplicate menu(s) removed
*WARNING* __deMakeBannerMenus ("maskLayoutXL"), duplicate menu(s) removed

deRegUserTriggers("maskLayout" nil 'trLeBannerTrigger nil)
procedure(trLeBannerTrigger(args)
list(bkLePulldownWindow())
)

deRegUserTriggers("maskLayoutXL" nil 'trLeBannerTrigger nil)
procedure(trLeBannerTrigger(args)
list(bkLePulldownWindow())
)

deRegUserTriggers("maskLayoutGXL" nil 'trLeBannerTrigger nil)
procedure(trLeBannerTrigger(args)
list(bkLePulldownWindow())
)

Thanks,

ManChak

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    ManChak,

    I don't see this problem with your code - so I can only assume that you must be adding (via some other mechanism) the menu more than once. Perhaps you have registered multiple different menu triggers each adding the same menu?

    I just defined:

    procedure(bkLePulldownWindow()
      hiCreatePulldownMenu('bkLePull "bk menu" list(hiCreateMenuItem(?name 'item1 ?itemText "ITEM 1" ?callback "println(12345)")))
    )

    and then loaded your code. It worked fine.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mctang
    mctang over 9 years ago

    Hi Andrew,

    1. nk you. You are correct. I have registered multiple different menu triggers each adding the same menu. If I run the following command a few times in the same layout window, will I get the following error message  (duplicate menu removed) ? The following warning appears when I invoke SKILL code from pulldown menu.

    deRegUserTriggers("maskLayoutXL" nil 'trLeBannerTrigger nil) procedure(trLeBannerTrigger(args) list(bkLePulldownWindow()))

    *WARNING* __deMakeBannerMenus ("maskLayoutXL"), duplicate menu(s) removed

    *WARNING* __deMakeBannerMenus ("maskLayoutXL"), duplicate menu(s) removed

    *WARNING* __deMakeBannerMenus ("maskLayoutXL"), duplicate menu(s) removed

    2. The SKILL contains he function which performs poly bias and "deRegUserTriggers("maskLayoutXL" nil 'trLeBannerTrigger nil) procedure(trLeBannerTrigger(args) list(bkLePulldownWindow()))". Thus, deRegUserTriggers command is called when I try to bias poly. Is it correct to include deRegUserTriggers in the Skill code which performs poly bias and createspulldown menu ?

    Thanks,

    ManChak

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    ManChak,

    I don't know which version you're using (this piece of generally important information was not mentioned by you), but as far as I know, repeatedly registering the same trigger function does not cause it to be duplicated - it ignores the duplicate. It would give a warning telling you this - such as:

    *WARNING* (DEBASE-102202): User menu trigger 'trLeBannerTrigger' is already registered for viewType maskLayoutXL.

    I have no idea what  your second question even means. It is so devoid of context that it's impossible to answer.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mctang
    mctang over 9 years ago

    Hi Andrew,

    Thank you for your info.

    My Virtuoso version is ICADV12.1-64b.

    ManChak 

    • 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