Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 12828
  • 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

Getting SKill Script From GUI History

Moaz Elshamy

How Can I get the Skill script behind my GUI command? 

For example, from the menu bar clicking on Connectivity -> XL Probe,  I want to add a bind key for opening XL Probe.  Hence, I need to get the skill command behind this to use hiSetBindKey. Is there a way to know the history of scripts performed by the GUI?

Moreover, is there a GUI way to set shortcuts for different tools in the menu bar? 

Thanks in advance.

Parents

  • Hi Moaz,

    A couple of approaches you could take. First of all, with the default bind keys, there already is a key binding for XL Probe (in the Connectivity menu for me it shows Shift+L). So if I run Options->Bindkey in the CIW (here's your "GUI way to set shortcuts") then you can pick the Layout application, and type "probe" in the search box at the top and you'll see:

    So here you can see it's lxHiProbe().

    Another way is to go to Options->Log Filter in the CIW and turn on the checkbox for \a (accelerated input...) and then invoke the toolbar/menu and you'll see the function appear in the CIW. All commands entered via the UI get recorded in the CDS.log file anyway (so that it can be replayed).

    A word of warning though - just because a command appears in the CDS.log/CIW, does not mean that's the right way to use it from SKILL - sometimes the expressions recorded are tied to a specific invocation or involve the UI. If you want the UI (e.g. as a bind key) then this is generally OK, but sometimes they need a little tweaking.

    Note that the annotations on the menus to show the keyboard shortcut is done automatically - if there's a bindkey associated with the same SKILL expression used as the menu callback then it will show up.

    Hope that helps!

    Andrew

Reply

  • Hi Moaz,

    A couple of approaches you could take. First of all, with the default bind keys, there already is a key binding for XL Probe (in the Connectivity menu for me it shows Shift+L). So if I run Options->Bindkey in the CIW (here's your "GUI way to set shortcuts") then you can pick the Layout application, and type "probe" in the search box at the top and you'll see:

    So here you can see it's lxHiProbe().

    Another way is to go to Options->Log Filter in the CIW and turn on the checkbox for \a (accelerated input...) and then invoke the toolbar/menu and you'll see the function appear in the CIW. All commands entered via the UI get recorded in the CDS.log file anyway (so that it can be replayed).

    A word of warning though - just because a command appears in the CDS.log/CIW, does not mean that's the right way to use it from SKILL - sometimes the expressions recorded are tied to a specific invocation or involve the UI. If you want the UI (e.g. as a bind key) then this is generally OK, but sometimes they need a little tweaking.

    Note that the annotations on the menus to show the keyboard shortcut is done automatically - if there's a bindkey associated with the same SKILL expression used as the menu callback then it will show up.

    Hope that helps!

    Andrew

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.