• 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. Skill to turn off ruler selection in Cadence 6.1 layout

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 144
  • Views 17542
  • 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

Skill to turn off ruler selection in Cadence 6.1 layout

LongTimeNovice
LongTimeNovice over 13 years ago

Hello.

 I'm trying to write some Skill code that will turn off ruler selection in Virtuoso 6.1 layout.

 When I do it manually, this appears in my CDS.log file:

 _pteHiGuidePropagateSelectability(dwindow('pteGuidePalette3) "Rulers" nil)

 pteGuidePalette3 is specific to the window in which I run the command.  It won't work in any other window, for instance pteGuidePalette10.

 Is there a way to use the command such that it will turn off ruler selection in all windows?  Is there a different command to do this?  Otherwise, is there a command that will determine the palette number of a given window?

 Thank you!

Steven.

 

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

    Stephen,

    Loading this from the .cdsinit won't work as is, because it only affects an existing palette. You could use something like this which fires any time you open a layout window (that might be annoying, because it will keep resetting it - so you might need to set flags to only do it once, maybe):

     procedure(MyPostInstallTrigger(args)
        leSetObjectSelectable("Boundaries" t)
        leSetObjectSelectable("P&R" t)
        leSetObjectSelectable("Area" t)
        leSetObjectSelectable("Snap" t)
        leSetObjectSelectable("Cluster" t)

        leSetObjectSelectable("ruler" nil )

        leSetObjectSelectable("Acknowledge Warning" nil)
        leSetObjectSelectable("Annotation" nil)
        leSetObjectSelectable("Critical Error" nil)
        leSetObjectSelectable("Error" nil)
        leSetObjectSelectable("Fatal" nil)
        leSetObjectSelectable("Info" nil)
        leSetObjectSelectable("Signed Off Critical Error" nil)
        leSetObjectSelectable("Signed Off Error" nil)
        leSetObjectSelectable("Warning" nil)
        leSetObjectSelectable("Markers" nil)
    )

    deRegUserTriggers("maskLayout" nil nil 'MyPostInstallTrigger)
    deRegUserTriggers("maskLayoutXL" nil nil 'MyPostInstallTrigger)

    Andrew

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

    Stephen,

    Loading this from the .cdsinit won't work as is, because it only affects an existing palette. You could use something like this which fires any time you open a layout window (that might be annoying, because it will keep resetting it - so you might need to set flags to only do it once, maybe):

     procedure(MyPostInstallTrigger(args)
        leSetObjectSelectable("Boundaries" t)
        leSetObjectSelectable("P&R" t)
        leSetObjectSelectable("Area" t)
        leSetObjectSelectable("Snap" t)
        leSetObjectSelectable("Cluster" t)

        leSetObjectSelectable("ruler" nil )

        leSetObjectSelectable("Acknowledge Warning" nil)
        leSetObjectSelectable("Annotation" nil)
        leSetObjectSelectable("Critical Error" nil)
        leSetObjectSelectable("Error" nil)
        leSetObjectSelectable("Fatal" nil)
        leSetObjectSelectable("Info" nil)
        leSetObjectSelectable("Signed Off Critical Error" nil)
        leSetObjectSelectable("Signed Off Error" nil)
        leSetObjectSelectable("Warning" nil)
        leSetObjectSelectable("Markers" nil)
    )

    deRegUserTriggers("maskLayout" nil nil 'MyPostInstallTrigger)
    deRegUserTriggers("maskLayoutXL" nil nil 'MyPostInstallTrigger)

    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