• 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. Allegro X Capture CIS
  3. Defining Custom Shortcut Keys on OrCAD Capture CIS v17....

Stats

  • State Not Answered
  • Replies 6
  • Subscribers 44
  • Views 15616
  • Members are here 0
More Content

Defining Custom Shortcut Keys on OrCAD Capture CIS v17.2

Gelo M
Gelo M over 4 years ago

Good day!

I'm currently using Cadence OrCAD Capture v.17.2.

Is there a way to bind custom keyboard shortcuts to functions accessible through mouse clicks?

For instance, I'd like to map "Signals" as shown below to, say, CTRL + ALT + S:

Signals

Thanks in advance!

  • Cancel
  • Sign in to reply
Parents
  • tennywhy
    0 tennywhy over 4 years ago

    i have do it , my be you could reference code below

    ###########################################

    # asume shortcut key set as Ctrl+W
    ##########################################
    proc shortcutSetInit { } {
    set shortCutArray {
    {"select Entire Net" "Ctrl+W" {MenuCommand "14844"}}
    }
    shortCutSetAll $shortCutArray
    }



    proc shortCutSetAll { LshortCutArray } {
    #puts "gos scs do"
    set shortCutArray $LshortCutArray
    set shortCutLength [llength $shortCutArray]

    for {set i 0} {$i < $shortCutLength} {incr i} {
    set shortCutElement [lindex $shortCutArray $i]
    shortcut_RegisterActions $shortCutElement
    }}

    proc shortcut_RegisterActions { shortCutElement } {
    set lEnableDS 1
    set shortcutName [lindex $shortCutElement 0]
    set shortCut [lindex $shortCutElement 1]
    set shortCutCommand [lindex $shortCutElement 2]
    set enable $lEnableDS
    RegisterAction $shortcutName "::shortcutSet::shortcut_Enabler" \
    $shortCut $shortCutCommand "Schematic"
    }


    proc ::shortcutSet::shortcut_Enabler {} {
    # Get the selected objects
    set lEnableDS 1
    return $lEnableDS
    }

    shortcutSetInit

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Gelo M
    0 Gelo M over 4 years ago in reply to tennywhy

    Hi Tenny,

    Much thanks for your reply.

    I have other questions:

    1. Where do I locate the file which I will edit to include the reference code?
    2. Is there a list of commands possible for remapping?
      For example, MenuCommand "14844".
      If I want to make a new shortcut for another command, how do I know which menu command number/ index to use? (ex: "14844") 
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • tennywhy
    0 tennywhy over 4 years ago in reply to Gelo M

    1. you should rename the file  shortcut.tcl. and put it in capautoload directory

    2. you should turn on the command display in command window use follow command , then you will see the menucommand when you operate.

    SetOptionBool Journaling TRUE

    SetOptionBool DisplayCommands TRUE

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • tennywhy
    0 tennywhy over 4 years ago in reply to Gelo M

    1. you should rename the file  shortcut.tcl. and put it in capautoload directory

    2. you should turn on the command display in command window use follow command , then you will see the menucommand when you operate.

    SetOptionBool Journaling TRUE

    SetOptionBool DisplayCommands TRUE

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • Gelo M
    0 Gelo M over 4 years ago in reply to tennywhy

    Thanks Tenny!

    I have set both Journaling and DisplayCommands to TRUE and now able to see corresponding MenuCommand indexes, like "14844" when using the "Signals" function.

    I created a file named shortcut.tcl under the folder C:\Cadence\SPB_17.2\tools\capture\tclscripts\capAutoLoad

    But I get the following error at startup of Capture CIS:


    Loading C:/Cadence/SPB_17.2/tools/capture/tclscripts/capAutoLoad/shortcut.tcl
    Error loading C:/Cadence/SPB_17.2/tools/capture/tclscripts/capAutoLoad/shortcut.tcl: invalid command name "proc ::shortcutSet::shortcut_Enabler"
    while executing
    "proc ::shortcutSet::shortcut_Enabler {} {
    # Get the selected objects
    set lEnableDS 1
    return $lEnableDS
    }"
    (file "C:/Cadence/SPB_17.2/tools/capture/tclscripts/capAutoLoad/shortcut.tcl" line 34)
    invoked from within
    "source $lFile"


    Here is line 34 of shortcut.tcl:

    Screenshot

    Thanks again in advance.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • SimonLym
    0 SimonLym over 1 year ago in reply to Gelo M

    Look like namespace issue.

    Add below at the begin of .tcl file.

    namespace eval ::capMenuUtil {} 

    Update: Don't try this way, capture22.1 crash everytime when i press ctrl +W.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • CadAP
    0 CadAP over 1 year ago in reply to Gelo M

    Look like you have you have namespace shortcutset but you have not used for proc shortcut_RegsiterAction? Try porc shoructset::shortcut_RegsiterAction also for shortcut_Enbale pass try to pass argument "args" only.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Cadence Guidelines

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