• 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. geClosePolygon() does not work correctly

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 12912
  • 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

geClosePolygon() does not work correctly

sparksu
sparksu over 15 years ago

I encountered a problem while using utility function "geClosePolygon()".

It is documented in "skdfref.pdf" :

**********************************************

         geClosePolygon(

                    d_cellViewId

                    l_points

                    t_snapMode

          ) =>  t/nil

*********************************************

But my codes did not work as it was described in file "skdfref.pdf".

geClosePolygon(deGetCellView() list(0:0 10:0 10:10) nil) => argument #3 should be a string.

geClosePolygon(deGetCellView() list(0:0 10:0 10:10) "orthogonal") => ((10.0 10.0) (0.0 10.0) (0.0 0.0)) 

geClosePolygon returns a list instead of t/nil.

 

My software version is 5.10.41.500.598.

And my document title is:

    Cadence Design Framework II SKILL Function Reference

    product version 6.31

    July 2007

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

    You should contact Cadence Customer Support to report bugs - that is the correct avenue for getting things fixed.

    As far as I can tell, the documentation is wrong - it should say that the third argument needs to be the snap mode (e.g. "anyAngle", "diagonal" etc) and not nil as in the example. The return value should be the resulting list of points for the closed polygon - it doesn't actually create the shape.

    However, I don't think it actually works correctly from my experiments - it does not appear to be trying to ensure an orthogonal polygon, and when I used anyAngle with certain point lists, I end up with a list of two points, which is clearly incorrect.

    That said, I can't think of any case where I'd actually want to use this function!

    Regards,

    Andrew.

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

    You should contact Cadence Customer Support to report bugs - that is the correct avenue for getting things fixed.

    As far as I can tell, the documentation is wrong - it should say that the third argument needs to be the snap mode (e.g. "anyAngle", "diagonal" etc) and not nil as in the example. The return value should be the resulting list of points for the closed polygon - it doesn't actually create the shape.

    However, I don't think it actually works correctly from my experiments - it does not appear to be trying to ensure an orthogonal polygon, and when I used anyAngle with certain point lists, I end up with a list of two points, which is clearly incorrect.

    That said, I can't think of any case where I'd actually want to use this function!

    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