Stats

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

Help me! Skill Experts!

sshinh

Hi, All!

I'm basic layout engineer.

Today, I made a skill script for layout metal layer on & off.

But, it's not run.

I don't know the reason.

Please, help me!

p.s> I use cadence IC6.1.5

-----------------------------------------------------------------------------------

procedure(view()

 leSetLayerVisible(list(\"M1\" \"drawing\") t)

 leSetLayerVisible(list(\"M2\" \"drawing\") t)

 hiRedraw()

) ;procedure

---------------------------------------------------------------------------------------

call bindkey setting

hiSetBindKeys("Layout" list(

list("Ctrl<Key>1"   "view()")

-----------------------------------------------------------------------------------------

CIW error message

 *Error* view : too few arguments (at least 1 expected, 0 given) - nil

------------------------------------------------------------------------------------------

Parents
  • Andrew Beckett

    In general we would recommend that any customer-written global functions use a prefix, ideally beginning with an uppercase letter (since uppercase prefixes are not used by Cadence) - to avoid clashing with other similar functions.

    As has been mentioned, view() is a Cadence-provided function and is write protected, so your function definition would fail.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    In general we would recommend that any customer-written global functions use a prefix, ideally beginning with an uppercase letter (since uppercase prefixes are not used by Cadence) - to avoid clashing with other similar functions.

    As has been mentioned, view() is a Cadence-provided function and is write protected, so your function definition would fail.

    Regards,

    Andrew.

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.