• 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. automatically OK form from within skill code

Stats

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

automatically OK form from within skill code

wangge
wangge over 10 years ago

Hello,

I am trying to write skill code that will invoke a form, and then automatically "click" OK, thereby executing the form's function, and then close/dismiss the form.  Here is the code:

dagDoNamedAction( dagNumToTool(3) dagGetObjectByPath( dagNumToTool(3) '( "ILBRootNode" "ILBRootClass"  "lib_test" "ILBLibraryClass" )) "Synchronize" )

hiiSetCurrentForm('ICL_SYNCHRONIZE_FORM)

hiFormDone(ICL_SYNCHRONIZE_FORM)

When I copy and paste these three lines into the CIW window,  it does exactly what I want it to do -- in other words, I can see the form pop up, then it goes away, and the function gets executed.

However, when I attempt to paste these three lines into skill code and execute the skill code, the form appears but does not "OK" automatically.  I have to click on the "OK" button, and then the form goes away.

I have spent a a lot of time searching for an answer, and have tried numerous attempts, but nothing seems to work.  For example, I tried implementing this code that I found on support.cadence.com:

   hiRegTimer("and(boundp('ddsDBox) ddsDBox

       hiDBoxOK(ddsDBox))

     and(boundp('ICL_SYNCHRONIZE_FORM)ICL_SYNCHRONIZE_FORM

       hiFormDone(ICL_SYNCHRONIZE_FORM))" 10)

Would be really greatful for any help!

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

    The timer starts from when the toplevel responds - essentially when the event loop kicks in. Since that won't happen until after the form is mapped on the screen and it's completed the callback, using 0 should be fine.

    Andrew.

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

    The timer starts from when the toplevel responds - essentially when the event loop kicks in. Since that won't happen until after the form is mapped on the screen and it's completed the callback, using 0 should be fine.

    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