• 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 Design
  3. 2 Stroke bindkey or state machine bindkey application

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 127
  • Views 16117
  • 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

2 Stroke bindkey or state machine bindkey application

bharath2k4
bharath2k4 over 11 years ago

Hi ,

 

 I remember using 2 stroke bindkey previously in IC5.14. Now I have moved, and currently using IC6.1.5 version Will the state machine  or 2 stroke bindkey work?

example of a 2 storke bindkey:

1. Press key<a>,

2. It expects one more key/stroke to complete a bindkey operation

 

Press key <a> and

if we press  <q> - say move

if we press <w> - say  copy

<e> - say rotate and so on..

 

like wise , This is not pressing 2 keys at a time, but one after the other 

<q><a> - rotate;

<q><s> - operation2;

<q><d> -operation3;

<q><f> -operation4 

 

I am not sure if I am understandable, Pardon me if I am not. I can explain again.

 

Thanks,

Bharath 

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

    My guess is that you didn't also call:

     abSeqBindKey->initBindKeys("Layout")

    You must do this to initialize the system. Without this, any registered key sequences will have no effect - this redefines all the letter and number keys to call this system. That's why you didn't get any errors, because the registered key sequence was never triggered. I did both the initBindKeys and the "fit" definition shown above, and it then worked fine in IC613. 

    The .ils suffix is required because the code is SKILL++ code; it takes advantage of lexical scoping to allow local functions and data, and this will not work with a .il suffix.

    I did not try a "state machine" type approach. I think this would be more complex to implement (at least more complex to maintain and register particular key sequences, potentially).

    Regards,

    Andrew.

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

    My guess is that you didn't also call:

     abSeqBindKey->initBindKeys("Layout")

    You must do this to initialize the system. Without this, any registered key sequences will have no effect - this redefines all the letter and number keys to call this system. That's why you didn't get any errors, because the registered key sequence was never triggered. I did both the initBindKeys and the "fit" definition shown above, and it then worked fine in IC613. 

    The .ils suffix is required because the code is SKILL++ code; it takes advantage of lexical scoping to allow local functions and data, and this will not work with a .il suffix.

    I did not try a "state machine" type approach. I think this would be more complex to implement (at least more complex to maintain and register particular key sequences, potentially).

    Regards,

    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