• 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. to set a bind key to show/hide dummy/odummy

Stats

  • Locked Locked
  • Replies 19
  • Subscribers 145
  • Views 8594
  • 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

to set a bind key to show/hide dummy/odummy

Weight66
Weight66 over 12 years ago
I'd  like to set a bind key to show/hide dummy/odummy, here is part of code:

procedure(ST_Lyt_ShowHide_Layers(Command PressedKey ShowDummy)       ;Available values for Command: >=1 to Add, <=1 to Remove and 0 to Hide all but selected one       ;Available values for ShowDummy: t to show dummy types and nil to keep dummy layers hidden       Lyt_Key_Layer_Assoc = '( ("0" 0) ("1" 1) ("2" 2) ("3" 3) ("4" 4) ("5" 5) ("6" 6) ("7" 7) ("8" 8) ("9" 9) ("`" 10) ("-" 11) )       Lyt_Sel_Layers = nth(nth(1 assoc(PressedKey Lyt_Key_Layer_Assoc)) Lyt_Layer_List)       Lyt_Show_Layer = nil       if((Command >= 0) then              leSetEntryLayer(list(nth(0 Lyt_Sel_Layers) nth(0 Lyt_Layer_Purposes)))              if((Command == 0) then                     leSetAllLayerVisible(nil)              )              foreach(Lyt_SLayer Lyt_Default_Layers                     foreach(Lyt_SPurpose Lyt_Layer_Purposes                           LytShowLayer = t                           if((Lyt_SPurpose == Lyt_Dummy_Purpose_Name) then                                  LytShowLayer = ShowDummy                           )                           leSetLayerVisible(list(Lyt_SLayer Lyt_SPurpose) LytShowLayer)                     )              )              Lyt_Show_Layer = t       )       if((Command >= -1) then              leSetEntryLayer(list(nth(0 Lyt_Default_Layers) nth(0 Lyt_Layer_Purposes)))       )       foreach(Lyt_SLayer Lyt_Sel_Layers              foreach(Lyt_SPurpose Lyt_Layer_Purposes                     LytShowLayer = Lyt_Show_Layer                     if((rexMatchp(strcat(".*" Lyt_Dummy_Purpose_Name ".*") Lyt_SPurpose) == t) then                           LytShowLayer = (ShowDummy && LytShowLayer)                     )                     leSetLayerVisible(list(Lyt_SLayer Lyt_SPurpose) LytShowLayer)              )       )       hiRedraw())

Thanks,
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Which version are you using? If IC61, then Alt bindkeys can't be defined by default (because Alt is used for Menu accellerators), unless you use:

    envSetVal("ui" "enableMenuShortcuts" 'boolean nil)

    to turn that feature off. For the CtrlShift 0, I could define it using Ctrl<Key>) on my keyboard (I suggest using the bindkey editor, and then when you press the key combination it tells you the sequence).

    Of course, I'm assuming that this is the problem and not to do with the actual code you're using. If course you can check that by just running the functions directly. If not, maybe you can state the version you're using too?

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Which version are you using? If IC61, then Alt bindkeys can't be defined by default (because Alt is used for Menu accellerators), unless you use:

    envSetVal("ui" "enableMenuShortcuts" 'boolean nil)

    to turn that feature off. For the CtrlShift 0, I could define it using Ctrl<Key>) on my keyboard (I suggest using the bindkey editor, and then when you press the key combination it tells you the sequence).

    Of course, I'm assuming that this is the problem and not to do with the actual code you're using. If course you can check that by just running the functions directly. If not, maybe you can state the version you're using too?

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information