• 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. A better understanding of hilight objects

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 142
  • Views 13389
  • 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

A better understanding of hilight objects

psill000
psill000 over 9 years ago

A better understanding of hilight objects

I understand how to create a hilight set and a hilight draw object
The problem I am having is when I want to draw another hilite set the first one disappears.
How do I switch to other hilight sets and keep the other hilight sets
Delete specific hilight set or delete hilight objects of a hilight set.

Some of my work in progress scripts to show my methodology or process ( some of the scripts may reference others that are not shown )
What I am looking for or inquiring about is a better understanding of the process of hilight sets and objects.
What am I missing from the scripts to draw multiple hilight sets?

procedure(stdLib_hilightMarker(shp xy mag)
let(    (mkrShpPts trans
        (hLpp '("hilite" "drawing4"))
        (hlSet  geGetCurrentWindowHilightSet(hiGetCurrentWindow()))
        )
if(null(boundp('hlSet)) || null(geIsValidHilightSet(hlSet)); || getWarn()
        stdLib_hiliteLpp(hLpp))

mkrShpPts       = stdLib_markerShape(shp)
trans           = list( list(xCoord(xy) yCoord(xy)) "R0" mag)
mkrShpPts       = stdLib_transPts(mkrShpPts trans)

if(hlSet && mkrShpPts geAddHilightLine(hlSet mkrShpPts))
); end of let
); end of stdLib_hilightMarker

procedure(stdLib_hiliteLpp(lpp)
let(    (hlSet)
        stdLib_SetValid(lpp)
        hlSet = geCreateWindowHilightSet(hiGetCurrentWindow() lpp t)
        gePushHilightStack(hlSet)
        hlSet~>enable = t
        geDrawHilightSet(geGetEditCellViewWindow(geGetEditCellView()) hlSet)
hlSet
); end of let
); end of stdLib_hiliteLpp

procedure(stdLib_deleteHiliteSet()
        when(geGetCurrentWindowHilightSet(getCurrentWindow())
        ;geDeleteHilightSet(hlSet))
        geDeleteAllWindowHilightSet(hiGetCurrentWindow()))
        )

Paul

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

    Hi Paul,

    I think your issue is because you're relying on using the current hilight set for the window. There's no reason why you can't have multiple hilight sets working independently - you just have to store them somewhere to retrieve them.

    I often do it by storing them as a property on the window - so:

    hiGetCurrentWindow()->mySet1=hlSet1
    hiGetCurrentWindow()->mySet1=hlSet2

    then you can retrieve them later. You can then enable/disable them as you see fit, delete them, recreate them - do whatever you want.

    Does that help?

    Regards,

    Andrew.

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

    Hi Paul,

    I think your issue is because you're relying on using the current hilight set for the window. There's no reason why you can't have multiple hilight sets working independently - you just have to store them somewhere to retrieve them.

    I often do it by storing them as a property on the window - so:

    hiGetCurrentWindow()->mySet1=hlSet1
    hiGetCurrentWindow()->mySet1=hlSet2

    then you can retrieve them later. You can then enable/disable them as you see fit, delete them, recreate them - do whatever you want.

    Does that help?

    Regards,

    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