• 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. callback when descending in layout hierarchy

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13461
  • 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

callback when descending in layout hierarchy

hihi
hihi over 12 years ago

 Hi,

I opened a layout from library manager and now I want to run a "callback" when I descend in the hierarchy and return to the top level. I found some information about "adding a preObjAccess Trigger  to ddGetObj" but I'm not sure whether this is the right way to solve my issue.

When I register this trigger with the code

 

ddRegTrigger( "PreObjAccess" 'testfunc)

procedure( testfunc(theLibName theCellName theViewName theFileName theContextId theMode)

 printf("%L %L %L %L %L %L" theLibName theCellName theViewName theFileName theContextId theMode)

);proc 

and I descend in the layout hierarchy this function prints a lot of lines looking like:

"testLib" "testCellView" "layout" nil nil nil

 "testLib" "testCellView" nil nil nil "r"

"testLib" "testCellView" "symbol" nil nil "r"

.........

Because of these outputs I'm not sure how to deal with this trigger. Perhaps it is not the right way to handle my needs.

 

Regards René

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    You should use deRegUserTriggers to do this - the args DPL passed into the triggers gives an action to say whether you were pushed, popped etc.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • hihi
    hihi over 12 years ago

     Hi Andrew,

    thanks a lot for your hint. I have implemented my function using this trigger and it works fine.

    Regards,

    René

    • 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