Stats

  • Locked Locked
  • Replies 2
  • Subscribers 144
  • Views 13201
  • 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

Bindkey: difference between IC61X and IC51X

Jerry1234

It looks like in IC61X, the bindkey is not case sensitive(assume capslock is not used), for example, in the manual, "P" is to createpin() although user need to input the lowercase "p" to invoke the function. 

 

However, in IC51X, bindkey is sensitive. I see lower case and uppercase bindkey everywhere in the drop down menu. Could you please elaborate the difference between these two major versions?

  • skillUser

    Hi Jerry,

    The bindkeys in IC61x are case sensitive.  In the menus, however, the keys would be shown as "P", "Shift-P" and "Ctrl-P" for the different cases of the key P, rather than "p", "P" and ?? - so I believe this was done for better readability and clarity.  The real difference is in the use of meta keys, for example, by default the Alt key is not used as a modifier in the IC61x versions as it is used as a menu accelerator key instead.

    Hopefully this answers your question.

    regards,

    Lawrence.

  • tweeks

    The punctuation characters are where things get interesting.  Which of these is correct?

    hiSetBindKey("Layout" "Shift<Key>3" "deselectMetal3Layer()")

    hiSetBindKey("Layout" "<Key>#" "deselectMetal3Layer()")

    You might assume that you could use either one interchangeably, and you would be partially correct in that assumption....  The trouble is that the system recognizes these as distinct keys, so if you bind "Shift<Key>3" to foo(), and "<Key>#" to bar(), either foo() or bar() will run when you type Shift+3 (I forget which), but rebinding the "wrong" one will have no effect in the layout editor.

    IIRC, it was order-dependent: which one the system accepted as "correct" depended on which one was loaded first!

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.