• 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. Ctrl fails to execute

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 142
  • Views 15802
  • 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

Ctrl fails to execute

archive
archive over 18 years ago

I am trying to bind a command to Ctrl but the command does not get called. I can bind this to other DrawThrus but not Ctrl. I see that the binding took when I check with hiGetBindKey. I can see that the ctrl press gets through too as the mouse clicks change to the ctrl bindings. Anyone have an idea why this would not take? Thanks


Originally posted in cdnusers.org by steven.labarre
  • Cancel
Parents
  • archive
    archive over 18 years ago

    This is sourcelink solution 11249750 - if you can access sourcelink.cadence.com take a look there.

    Essentially it's a bug, and you need to also define the bindkey for Ctrl Btn2Down - can be a dummy SKILL expression that gets evaluated (e.g. "t").

    The same thing happens with shift modifiers, and in fact happens for all mouse drawthrus (1,2,3) - but you don't normally notice it for the other two, because they usually have the BtnXDown bindkeys defined.

    It's fixed in IC610 - there will not be a need to define the Btn2Down binding with the same modifier then.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    This is sourcelink solution 11249750 - if you can access sourcelink.cadence.com take a look there.

    Essentially it's a bug, and you need to also define the bindkey for Ctrl Btn2Down - can be a dummy SKILL expression that gets evaluated (e.g. "t").

    The same thing happens with shift modifiers, and in fact happens for all mouse drawthrus (1,2,3) - but you don't normally notice it for the other two, because they usually have the BtnXDown bindkeys defined.

    It's fixed in IC610 - there will not be a need to define the Btn2Down binding with the same modifier then.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • 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