• 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. Running 2 procedures or function in 1 bindkey

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 144
  • Views 14986
  • 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

Running 2 procedures or function in 1 bindkey

GDCRA
GDCRA over 8 years ago

Hi,

I was spying on skill command in CIW when I am doing some graphical actions such as clicking netlistcreat form and clicking "Apply" in order to create netlist.

I thought I will able to create keybinding to run this step, so I was trying

hiSetBindKey("Schematics" "<Key>F12" "xcreateNetlist() _hiFormApplyCB(xcreateNetlistForm)")

But its on working. For some reason, it get stucked at 1st stage of opening form. When I close this form, it perform 2nd part of nestling. So its waiting for something between step 1 and step 2.

Can someone help here ?

Thanks

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

    Hi Lawrence,

    <pedantryAlert>

    Whilst I tend to follow the convention you suggest (although generally speaking I write in LISP syntax rather than using operators at all, as you know), strictly speaking the only difference between ~> and -> is when the left-hand-side is a list.

    If the left-hand-side is a singleton object, they are equivalent. If the left-hand-side is a list, then -> treats the list as a disembodied property list; the ~> operator does an implicit "foreach mapcar" across the list - so in other words if you do theList~>prop it will return a list of all the resulting values that you'd get if you did ~>prop for each member of the list.

    </pedantryAlert>

    Regards,

    Andrew.

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

    Hi Lawrence,

    <pedantryAlert>

    Whilst I tend to follow the convention you suggest (although generally speaking I write in LISP syntax rather than using operators at all, as you know), strictly speaking the only difference between ~> and -> is when the left-hand-side is a list.

    If the left-hand-side is a singleton object, they are equivalent. If the left-hand-side is a list, then -> treats the list as a disembodied property list; the ~> operator does an implicit "foreach mapcar" across the list - so in other words if you do theList~>prop it will return a list of all the resulting values that you'd get if you did ~>prop for each member of the list.

    </pedantryAlert>

    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