• 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. PCB Design
  3. Funckey and Alias in Env file work erratically in latest...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 165
  • Views 18733
  • Members are here 0
More Content
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

Funckey and Alias in Env file work erratically in latest Hot Patch

Jeri
Jeri over 7 years ago

Hi, is any one else going crazy with funckey call outs while in Allegro?  Ever since 17.2 HP 032 Cadence has done something that most of my funckey stop working.

E.g.  I use a Macro keyboard with all of the keyboard keys mapped to it.  I start a route with a key on the keyboard then complete the route with another key on the keyboard which is mapped to end.

It seems to work for a little bit and then suddenly it won't do anything.  I can't complete my route by hitting the end key.  Seems if I right click the mouse and go back to the canvas the macro keyboard starts working.

If I have to right click the mouse I might as well hit the end on the popup instead!  Defeats the purpose of a macro keyboard!!

I've had tech support look into it but they asked to change all of my alias to funckey commands instead but that didn't work.  I've rolled back to HP 030 twice now.

Here is what my Env looks like.

alias F5 replay LibrarySetup
alias F6 replay Package_height
alias F7 replay Padstack_replace
alias F8 replay Padstack_edit
alias F9 replay view_routing
alias F10 replay view_bottom
alias F11 replay view_top
alias F12 replay view_top-bot

funckey Pgup zoom in
funckey Pgdown zoom out
funckey Home zoom fit
funckey Del delete
funckey Esc cancel
funckey Insert next
funckey f 'settoggle gridvalue 0.1 0.01; replay set-grid $gridvalue;echo grid = $gridvalue'
funckey F 'settoggle gridvalue 0.1 0.01; replay set-grid $gridvalue;echo grid = $gridvalue'
funckey g 'settoggle gridvalue 1 5; replay set-grid $gridvalue;echo grid = $gridvalue'
funckey G 'settoggle gridvalue 1 5; replay set-grid $gridvalue;echo grid = $gridvalue'
funckey m 'settoggle gridvalue 3.937 15.748 19.685; replay set-grid $gridvalue;echo grid = $gridvalue'
funckey M 'settoggle gridvalue 3.937 15.748 19.685; replay set-grid $gridvalue;echo grid = $gridvalue'
funckey 0 replay slide
funckey 1 "add connect"
funckey 2 replay find_groups
funckey * toggle
funckey End Done
funckey / "pop neck"
funckey 3 replay full_contact
funckey 4 move
funckey 5 iangle 90
funckey 6 "prepopup;pop mirror"
funckey 7 replay find_symbol
funckey 8 replay find_trace_via
funckey 9 replay find_net
funckey w 'settoggle minw 10 12 15; setwindow form.mini; FORM mini acon_line_width $minw; setwindow pcb'
funckey s "Spin;iangle 45"
funckey S "Spin;iangle 90"

  • Cancel
Parents
  • Dale Peterson
    Dale Peterson over 7 years ago

    Yes, my keys comes an go. When they go I get pull downs instead. Example, I have my "u" key defined to do something that I like. It works for awhile just fine.  But, then out of the blue. The "Setup" menu starts to drops down and interrupts my key function. It acts up as if I had pressed the Alt key. The u key plus the alt key is the correct response for bringing down the "Setup" menu. This I know. Because the "u" is underlined in the word startup. But remember, I did not press the alt key. My key assignments have been working fine for years until I loaded in the 37 hot fix. Now all my keys are acting up. My temp remedy is to hit the ESC key. Or I reload the job to get it to stop for a short period of time. by the way, even my scroll on my mouse stops too. VERY VERY BAD BUG. BEWARED!!!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Dale Peterson
    Dale Peterson over 7 years ago

    Yes, my keys comes an go. When they go I get pull downs instead. Example, I have my "u" key defined to do something that I like. It works for awhile just fine.  But, then out of the blue. The "Setup" menu starts to drops down and interrupts my key function. It acts up as if I had pressed the Alt key. The u key plus the alt key is the correct response for bringing down the "Setup" menu. This I know. Because the "u" is underlined in the word startup. But remember, I did not press the alt key. My key assignments have been working fine for years until I loaded in the 37 hot fix. Now all my keys are acting up. My temp remedy is to hit the ESC key. Or I reload the job to get it to stop for a short period of time. by the way, even my scroll on my mouse stops too. VERY VERY BAD BUG. BEWARED!!!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • lcan
    lcan over 7 years ago in reply to Dale Peterson

    Wow. for about the past month I thought this was something I had messed up with no good way to debug the process I use do define alias and funkeys which is dependant on the Application mode I am in. Patiently waiting for Hotfix 38....  Have a great weekend.

    Bill

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • excellon1
    excellon1 over 7 years ago in reply to lcan

    Guys, SO38 is out now with literally a plethora of fixes (186) that include UI fixes for function keys and hot keys etc.

    Paul.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Dale Peterson
    Dale Peterson over 7 years ago in reply to excellon1

    Paul,

    My issues have gone away thanks to Hotfix 38. Yea!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Jeri
    Jeri over 7 years ago in reply to Dale Peterson

    Yes, they have fixed all of my issues.  Seems faster too.  Finally!!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • excellon1
    excellon1 over 7 years ago in reply to Dale Peterson

    Well very cool Dale,

    That hot key issue was kind of interesting, I can honestly say I never had a problem with them in the prior cuts of 17.x. On a related note MS did push down an update
    a few months back that caused me some issues. Basically the mouse would go away for a short time.. During those periods I did notice that hot keys failed to work.
    It was almost like a quick glitch... Kind of wierd.

    Anyway, all seems good now. Yay !

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