• 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. Print output to cursor in the layout window?

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 144
  • Views 15542
  • 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

Print output to cursor in the layout window?

blankman
blankman over 14 years ago

Hi all, im looking to output the result of a function to hover next to the cursor in the layout window...

For instance say I want to compute the width of a selected path............

hiSetBindKey("Layout" "Alt<key>KP_Delete" "geGetSelSet()~>width")

Is it possible to ouput the path width to appear next to the cursor in the layout window rather than the CIW for ease of viewing?

Or alternatively is it possible to print somewhere in the layout window viewing area?

Thanks

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

    OK, here's some code. It's not polished, not fully tested, but might give you a starting point...

    /* abDynamicDisplay.il

    Author A.D.Beckett
    Group Custom IC (UK), Cadence Design Systems Ltd.
    Language SKILL
    Date Apr 28, 2011
    Modified
    By

    Example of dynamic display in IC5141. Uses leRegUserObjectSelectionFilter
    to track what the user is over - and then builds a message to display.
    The highlight label is displayed at the cursor location.

    Call abDynamicDisplay(t) to enable (pass nil to disable).

    ; can set these properties to alter how the highlight labels are drawn
    abDynamicDisplay.lpp='("y0" "drawing")
    abDynamicDisplay.height=0.2
    abDynamicDisplay.font="stick"
    abDynamicDisplay.orient="R0"
    abDynamicDisplay.justify="lowerLeft"

    The code is not polished, not thoroughly tested. It just illustrates
    the idea.

    In IC61 this is completely obsoleted by the Info Balloon capability.

    IC5141 also has "Shape Information" which gives some of this kind of
    display, but what is displayed is hardcoded.

    ***************************************************

    SCCS Info: @(#) abDynamicDisplay.il 04/28/11.13:36:35 1.1

    */


    /***************************************************************
    * *
    * abDynamicDisplaySelectFilter(fig) *
    * *
    * Filter function to do the dynamic display. *
    * *
    ***************************************************************/


    procedure(abDynamicDisplaySelectFilter(fig)
    let((win hs message point)
    win=geGetEditCellViewWindow(fig~>cellView)
    ;--------------------------------------------------------------------
    ; If the object is the same as last time, don't re-generate
    ;--------------------------------------------------------------------
    unless(fig==abDynamicDisplay.lastObject
    hs=win~>abDynDisplayHS
    when(geIsValidHilightSet(hs) geDeleteHilightSet(hs))
    ;----------------------------------------------------------------
    ; Customize this bit to reflect what is shown for each object
    ;----------------------------------------------------------------
    case(fig~>objType
    ("path"
    sprintf(message "Layer: %s Width: %g" fig~>layerName fig~>width)
    )
    )
    when(message
    abDynamicDisplay.lastObject=fig
    point=hiGetPoint(win)
    when(point
    hs=geCreateHilightSet(fig~>cellView
    abDynamicDisplay.lpp || '("y0" "drawing"))
    win~>abDynDisplayHS=hs
    geAddHilightLabel(
    hs
    geWindowToEditPoint(win point)
    message
    abDynamicDisplay.justify || "lowerLeft"
    abDynamicDisplay.orient || "R0"
    abDynamicDisplay.font || "stick"
    abDynamicDisplay.height || 0.2
    nil
    )
    hs->enable=t
    geRefresh()
    )
    )
    )
    ;--------------------------------------------------------------------
    ; Always return t because don't want to do any actual filtering
    ;--------------------------------------------------------------------
    t
    ))

    /***************************************************************
    * *
    * abDynamicDisplay(enable) *
    * *
    * Enable or display the dynamic display *
    * *
    ***************************************************************/


    procedure(abDynamicDisplay(enable)
    if(enable then
    leRegUserObjectSelectionFilter("abDynamicDisplaySelectFilter")
    else
    leUnregUserObjectSelectionFilter()
    )
    )

     

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

    OK, here's some code. It's not polished, not fully tested, but might give you a starting point...

    /* abDynamicDisplay.il

    Author A.D.Beckett
    Group Custom IC (UK), Cadence Design Systems Ltd.
    Language SKILL
    Date Apr 28, 2011
    Modified
    By

    Example of dynamic display in IC5141. Uses leRegUserObjectSelectionFilter
    to track what the user is over - and then builds a message to display.
    The highlight label is displayed at the cursor location.

    Call abDynamicDisplay(t) to enable (pass nil to disable).

    ; can set these properties to alter how the highlight labels are drawn
    abDynamicDisplay.lpp='("y0" "drawing")
    abDynamicDisplay.height=0.2
    abDynamicDisplay.font="stick"
    abDynamicDisplay.orient="R0"
    abDynamicDisplay.justify="lowerLeft"

    The code is not polished, not thoroughly tested. It just illustrates
    the idea.

    In IC61 this is completely obsoleted by the Info Balloon capability.

    IC5141 also has "Shape Information" which gives some of this kind of
    display, but what is displayed is hardcoded.

    ***************************************************

    SCCS Info: @(#) abDynamicDisplay.il 04/28/11.13:36:35 1.1

    */


    /***************************************************************
    * *
    * abDynamicDisplaySelectFilter(fig) *
    * *
    * Filter function to do the dynamic display. *
    * *
    ***************************************************************/


    procedure(abDynamicDisplaySelectFilter(fig)
    let((win hs message point)
    win=geGetEditCellViewWindow(fig~>cellView)
    ;--------------------------------------------------------------------
    ; If the object is the same as last time, don't re-generate
    ;--------------------------------------------------------------------
    unless(fig==abDynamicDisplay.lastObject
    hs=win~>abDynDisplayHS
    when(geIsValidHilightSet(hs) geDeleteHilightSet(hs))
    ;----------------------------------------------------------------
    ; Customize this bit to reflect what is shown for each object
    ;----------------------------------------------------------------
    case(fig~>objType
    ("path"
    sprintf(message "Layer: %s Width: %g" fig~>layerName fig~>width)
    )
    )
    when(message
    abDynamicDisplay.lastObject=fig
    point=hiGetPoint(win)
    when(point
    hs=geCreateHilightSet(fig~>cellView
    abDynamicDisplay.lpp || '("y0" "drawing"))
    win~>abDynDisplayHS=hs
    geAddHilightLabel(
    hs
    geWindowToEditPoint(win point)
    message
    abDynamicDisplay.justify || "lowerLeft"
    abDynamicDisplay.orient || "R0"
    abDynamicDisplay.font || "stick"
    abDynamicDisplay.height || 0.2
    nil
    )
    hs->enable=t
    geRefresh()
    )
    )
    )
    ;--------------------------------------------------------------------
    ; Always return t because don't want to do any actual filtering
    ;--------------------------------------------------------------------
    t
    ))

    /***************************************************************
    * *
    * abDynamicDisplay(enable) *
    * *
    * Enable or display the dynamic display *
    * *
    ***************************************************************/


    procedure(abDynamicDisplay(enable)
    if(enable then
    leRegUserObjectSelectionFilter("abDynamicDisplaySelectFilter")
    else
    leUnregUserObjectSelectionFilter()
    )
    )

     

    • 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