• 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 Design
  3. Schematic Probe highlight thickness

Stats

  • Locked Locked
  • Replies 18
  • Subscribers 128
  • Views 34363
  • 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

Schematic Probe highlight thickness

acook
acook over 11 years ago
I am trying to do something like CCR 1844262. I have a common SKILL file designers in my group load and I would like to implement changing the probe width there (if that is even the best way to do it).

Changing the default display.drf in the cadence install directory is not an option.

I could not find anything on how to change display settings using only SKILL and not a drf.
  • Cancel
  • Karev11
    Karev11 over 10 years ago

    Hi Andrew,

    I also have question about Schematic Probe highlight thickness. I'm using icfb 5141

    The issue I have is that by default, when  trying to highlight a node (click 9), the highlight is blinking but very dim  and thin, making it hard to identify especially with big schematic. In my previous company there's a CAD guy who wrote skill code, and when we load it in CIW, the highlight is thicker and everything is good. Now I don't have that luxury anymore, wonder if you could help me here: thicker highlight is all that I need.

    thanks,!

    Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 10 years ago

    Hi Kevin,

    Try something like this (which is essentially what Andrew posted earlier in this thread):

    packets = foreach(mapcar lay '("y0" "y1" "y2" "y3" "y4" "y5" "y6" "y7" "y8" "y9")
      pack = drGetPacket("display" strcat(lay "_drawing"))
      setcar(cdddr(pack) "thickLine")
      apply('drSetPacket pack)
      pack)
    If you need to return the y0-y9 thicknesses to normal use this:
    foreach(pack packets
      setcar(cdddr(pack) "solid”)
      apply('drSetPacket pack))
     

    If 'thickLine' is too thick, you can try 'thickLine2' instead.
    Hopefully this is what you wanted?

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Karev11
    Karev11 over 10 years ago

    Thanks a lot Lawrence,  this is exactly what I wanted.

    Best,

    Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • akumar2886
    akumar2886 over 9 years ago
    Hi skillUser, Is there a way such that "save display information" box doesn't come up when cadence is closed after running your code? Regards, Adi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Adi,

    No. The drLoadDrf() has an option to make changes without asking you to save at the end, but drSetPacket does not. There's a CCR 1149024 asking for this, but it's not been implemented yet (and isn't planned at the moment - but that may get reconsidered).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 9 years ago

    There is a hacky workaround, however, to automatically dismiss the "Save Display Information" pop-up. Put the following in your .cdsinit startup file:

    
    ;; automatically close the "Save Display Information" form when exiting
    procedure(CCSsuppressDispForm()
      hiRegTimer("hiFormCancel(techSaveDrmForm)" 10) 
    )
    
    regExitBefore('CCSsuppressDispForm)
    

    Hopefully this will help?

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • akumar2886
    akumar2886 over 9 years ago

    Thank you for the information, Andrew

    Best regards

    Adi

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • akumar2886
    akumar2886 over 9 years ago
    Thanks, skillUser
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
<

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