• 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. Cannot overwrite EnterFunction Command for default bindkey...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 16338
  • 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

Cannot overwrite EnterFunction Command for default bindkey definition

Pedro Paro Filho
Pedro Paro Filho over 8 years ago

Dears,


Minor problem, but I cannot overwrite the default bindkey definition with my own SKILL command.
By default, the layout command for "Ctrl <Btn4>" is geScroll(nil "n" nil) with the EnterFunction Command weScrollOrCycleUpWireViaAlignment().

If I try to change the bindkey command to hiZoomInAtMouse(), (loaded via .cdsinit or even through the Bindkey Editor), the EnterFunction command is not removed from the previous definition, and the bindkey doesn't work properly.

This is the Skill command I introduced in my .cdsinit.


hiSetBindKey("Layout" "Ctrl<Btn4Down>" "hiZoomInAtMouse()")

Any hints?

The virtuoso version is IC6.1.6-64b.500.7

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    I'm not sure why you think this is tricky. The bindkey in normal mode is different from in enter function mode - so if using hiSetBindKey and you want to set or erase both the normal and enter function modes, you have to call hiSetBindKey twice, which is what you've done here with your step 3.

    After many releases of having no bind keys by default, we made a change a few releases back to automatically load the bindkeys in <ICinstDir>/share/cdssetup/dfII/bindkeys (these can also be overridden by the setup.loc mechanism) rather than requiring everyone to load a full set of bind keys from their .cdsinit file. However, what that means is that if you want to erase one of the defaults, you have to set it to blank.

    You could also just do:

    hiSetBindKeys("Layout" list(
      list("Ctrl<Btn4Down>" "hiZoomInAtMouse()" "")
    ))

    which would do the same thing. This function allows you to set both the normal and the enter function bind keys at the same time.

    That's the function used that  you see if you save from the Options->BindKey form.

    Andrew.

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

    I'm not sure why you think this is tricky. The bindkey in normal mode is different from in enter function mode - so if using hiSetBindKey and you want to set or erase both the normal and enter function modes, you have to call hiSetBindKey twice, which is what you've done here with your step 3.

    After many releases of having no bind keys by default, we made a change a few releases back to automatically load the bindkeys in <ICinstDir>/share/cdssetup/dfII/bindkeys (these can also be overridden by the setup.loc mechanism) rather than requiring everyone to load a full set of bind keys from their .cdsinit file. However, what that means is that if you want to erase one of the defaults, you have to set it to blank.

    You could also just do:

    hiSetBindKeys("Layout" list(
      list("Ctrl<Btn4Down>" "hiZoomInAtMouse()" "")
    ))

    which would do the same thing. This function allows you to set both the normal and the enter function bind keys at the same time.

    That's the function used that  you see if you save from the Options->BindKey form.

    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