• 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. How to let enterPoint wait mouse click one by one

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 15232
  • 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

How to let enterPoint wait mouse click one by one

zhisong
zhisong over 14 years ago

Hi,

I'm trying to code multi label for layout, just like in schematic.

Now I have code like this, in order that code will wait my next mouse click to get to location.

for(i 1 3 loc=enterPoint(?prompts list("next")) print(loc) i++)

But after my first click, SKILL will finish the 3 loops at once. It doesn't wait for my 2nd and 3rd click.

Why? Please correct me.

Thanks

-Jason

  • Cancel
Parents
  • pzakel
    pzakel over 14 years ago

    Noting that enterPoints() is indeed the better solution, I was surprised that the enterPoint() loop did not work.  I just tried coding a routine that used enterPoint() in a loop, but assigned each point to an array, and it worked fine in IC 6.1.5 -- it waited for each point and returned all three points in the array.

     Jason, in which release were you trying this?

     -Pete Z.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • pzakel
    pzakel over 14 years ago

    Noting that enterPoints() is indeed the better solution, I was surprised that the enterPoint() loop did not work.  I just tried coding a routine that used enterPoint() in a loop, but assigned each point to an array, and it worked fine in IC 6.1.5 -- it waited for each point and returned all three points in the array.

     Jason, in which release were you trying this?

     -Pete Z.

    • 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