Stats

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

textDisplays doesn't exist till you edit pin name height

swdesigner

 I'm writing some skill code to increase all pin names 10%.

 First step is to do this for one pin. I find that

 cvId~>terminals gives me the terminals.

aPin = car(cvId~>terminals) gives me one pin to work with.

If I 'q' the pin name on the schematic after selecting it (why doesn't geGetSelSet give nil when a pin name is selected??), I see 0.0625.

 However, aPin~>textDisplays is nil

Only if I change the value using the form, does aPin~>textDisplays exist. Then I can use aPin~>textDisplays~>height to change the size.

Question : What should I do to avoid the human interaction?

Thanks!

  • skillUser

    Well, there is a dbCreateTextDisplay SKILL command, this may give you what you want. I'm guessing a little bit here, since there is a distinct lack of detail (schematic or layout?  which software version?)

    Regards,

    Lawrence.

  • Andrew Beckett

    Normally the textDisplays for pins get created straightaway. Some textDisplays only created when an instance label is moved or changed in some way, because the label (or textDisplay) only exists in the master - and the act of doing that then obscures the label from the master (it doesn't display it).

    When I checked in the schematic editor in IC5141 and IC614, creating a pin caused the textDisplay to get created - and I can manipulate it for all terminals by doing cv~>terminals~>textDisplays~>height=... 

    Perhaps it is depended on the library your pins are coming from? 

    I think more detail is needed, as Lawrence suggested.

    Regards,

    Andrew.

  • swdesigner

    I'm in 5.10.41.500.6.141

    Thanks, I see dbCreateTextDisplay. Now, is there a way to access the textDisplays from the master and create that for the instance? I only want to change the height. I see that thisPin~>?? shows nil for assocTextDisplays so what must one do? How does the properties editor handle this?

    This is for a schematic view.  The pins are coming from the "basic" library.

    Thanks for helping. I'm trying to set up Ctrl+] and Ctrl-[ as bindkeys to make pin names bigger and smaller. When I fit the schematic to a full-screen window, I like to see all pin names without zooming.

  • swdesigner

     Any thoughts Andrew, Lawrence? This would really boost my productivity when I'm doing reverse engineering.

     Thanks

  • swdesigner

    Don't use cellView terminals, use shapes. This works :

     

    cv = geGetWindowCellView()
    printf("Processing %s\n", cv~>cellName)
    (if !( cv~>mode == "r")
        then
            foreach( shape cv~>shapes
                if( (equal("label" shape~>purpose) && equal("pin" car(shape~>lpp) ) )
                    then
                        shape~>height = 1.1*shape~>height
                )
            )
        else
            println("Sorry, exiting due to read-only mode")
    )

  • swdesigner

    However, when I do that, I notice that Fit (shortcut : f) no longer shows the schematic correctly - some of the pin names are outside the viewing area.

     

    Anyone have a clue about that?

     

    Thanks!

  • swdesigner
    Is there a property of the cellview that Virtuoso refers to to fit the schematic? How can I update this? When I go through the form, to update pin name height, this comes out okay, but not if I use my skill that manipulates shape~>height. Thanks!
  • Andrew Beckett

    It looks at the ~>bBox attribute of the cellView. This should update automatically, but you can call dbComputeBBox(cvId) to force it to recompute it.

    Regards,

    Andrew.

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.