Stats

  • Locked Locked
  • Replies 6
  • Subscribers 142
  • Views 15019
  • 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

Toggle Instances Selectable With One Bindkey

buttonGuy

Hello,

I am new to skill and my problem is as follows: in Layout, there is an Objects palette that contains the visible & selectable options for Shapes, Instances, Fluid Guardring, Mosaic, Pins, Vias, etc. I want to be able to toggle the Selectable checkbox of the “Instances” with the use of a single bindkey. Currently, I have two bind keys set to make it selectable and not selectable:

z bindkey: _pteHiObjectSetSelectability(dwindow(‘pteObjectPalette2) “Instances” nil)·

Shift+z bindkey: _pteHiObjectSetSelectability(dwindow(‘pteObjectPalette2) “Instances” t)

Any suggestions would be greatly appreciated.

 Thanks!

Parents

  •  You are correct with your statements, Andrew. I had heard about the performance issue but that was before I joined Cadence and I ignored it till it went away.

    I like Lawrence's solution where the conditional is eliminated.

    pteSetSelectable("Instances" !pteIsSelectable("Instances" "Objects") "Objects")

    I forgot that the three statements generate an error (price of being retired). 

    There were several cases when I an AE where the user added an additional clause and did not get the results they had expected. I remember being scolded by a customer when I sent back their code with a 5 letter fix, adding a then statement, ranting about how SKILL was such a "confusing" language. 

    "Always include a then/else"

Reply

  •  You are correct with your statements, Andrew. I had heard about the performance issue but that was before I joined Cadence and I ignored it till it went away.

    I like Lawrence's solution where the conditional is eliminated.

    pteSetSelectable("Instances" !pteIsSelectable("Instances" "Objects") "Objects")

    I forgot that the three statements generate an error (price of being retired). 

    There were several cases when I an AE where the user added an additional clause and did not get the results they had expected. I remember being scolded by a customer when I sent back their code with a 5 letter fix, adding a then statement, ranting about how SKILL was such a "confusing" language. 

    "Always include a then/else"

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.