• 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. envSetVal "labelHeight" (IC6) from .cdsinit

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 5461
  • 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

envSetVal "labelHeight" (IC6) from .cdsinit

stuso
stuso over 13 years ago

 hi guys,

i can do the following in my ciw/virtuoso window:

envSetVal( "layout" "labelHeight" 'float 0.05 )

and using envGetVal it seems to have worked ok.

However when i add the same line to my .cdsinit andstart a new cadence session it does not sseem to have any effect. I'm sure my .cdsinit is being loaded as i have some print statements in there at the start and end of the .cdsinit.

Thanks

Stu

FYI: i am trying to set the default label size for pins for when i generate/update with XL

 

 

 

  • Cancel
Parents
  • dmay
    dmay over 13 years ago

    I wouldn't say it is bad practice, just a matter of preference. There are so many variables you can set to customize forms, tools, windows, etc, that the .cdsenv file is a convenient place to put them. The .cdsinit file is a great place to put skill code you want to run at startup (load personal bindkeys, display the library manager, etc). Some of the options forms have a convenient feature to load/save the .cdsenv file, so by having your settings in the .cdsenv, you can quickly revert back to your personal defaults.

    Derek 

    stuso said:

    i have been trying to put all my settings in the one file, infact at this time i do not have a .cdsenv at all (i use envSetVal in the .cdsinit for all my environment variable settings).

    Is this bad practice?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dmay
    dmay over 13 years ago

    I wouldn't say it is bad practice, just a matter of preference. There are so many variables you can set to customize forms, tools, windows, etc, that the .cdsenv file is a convenient place to put them. The .cdsinit file is a great place to put skill code you want to run at startup (load personal bindkeys, display the library manager, etc). Some of the options forms have a convenient feature to load/save the .cdsenv file, so by having your settings in the .cdsenv, you can quickly revert back to your personal defaults.

    Derek 

    stuso said:

    i have been trying to put all my settings in the one file, infact at this time i do not have a .cdsenv at all (i use envSetVal in the .cdsinit for all my environment variable settings).

    Is this bad practice?

    • 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