• 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. how to get the name of a dockable window in a Layout wi...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 2383
  • 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

how to get the name of a dockable window in a Layout window

mdydyz112
mdydyz112 over 7 years ago

Hi all,

I want to find the name of a dockable window within a Layout window. 

For example, in one of my layouts, i turn on the 'Track Pattern' window on the right of my layout window and in the CIW window, i see the following cmd show up, 'hiUnmapWindow(dwindow('TPAsst_9')) when(dwindow('TPAsst_9) hiMapWindow(dwindow('TPAsst_9)))'. From this cmd, TPAsst_9 is the name of the Track Pattern window. however, if i open another layout, and open the Track Pattern window, the name of the Track Pattern window will be different. 

so my question is, is there a way to find the name of the Tracck Pattern window??

Thanks. Let me know if I didnt express the question clearly.

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

    If you want to find the dock window id, then you can do:

    dwindowId=deFindAssistant("Track Pattern" hiGetSessionWindow(hiGetCurrentWindow()))

    If you then want to find the name (which probably isn't necessary if you have the id above, but including for completeness), it would be:

    dwindowId->hiHandle

    BTW, it does seem that the deFindAssistant function works with just hiGetCurrentWindow() passed to it (not just the session window), but the documentation doesn't mention that as being supported - so probably best to provide the session window.

    Regards,

    Andrew.

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

    If you want to find the dock window id, then you can do:

    dwindowId=deFindAssistant("Track Pattern" hiGetSessionWindow(hiGetCurrentWindow()))

    If you then want to find the name (which probably isn't necessary if you have the id above, but including for completeness), it would be:

    dwindowId->hiHandle

    BTW, it does seem that the deFindAssistant function works with just hiGetCurrentWindow() passed to it (not just the session window), but the documentation doesn't mention that as being supported - so probably best to provide the session window.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • mdydyz112
    mdydyz112 over 7 years ago in reply to Andrew Beckett

    hi Andrew, 

    thanks alot, that works. however, it only works if i have the Track Pattern window opened once (when i first open a layout). 

    For example, if a layout is opened the first time (after I launch cadence), deFindAssistant("Track Pattern" hiGetSessionWindow(hiGetCurrentWindow())) returns nil. I have to open the track pattern window first, then run the above line and it will return the window ID.

    Is there a way to find the window ID/name without having to open the Track pattern window? 

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to mdydyz112

    I'd not checked that, sorry.

    Looking through the code, there's no real public interface (or even a single SKILL private interface) to initialise the assistant (it doesn't get created until the first time it is displayed - essentially lazy evaluation to save start up time in the event of not using it) - it's only when it is first started (even that there's no interface for).

    This would need you to contact customer support for a request for a function to do this. It probably will be best if you can explain why you need the name of the object so that the correct function is made available in case there's a simpler solution to your underlying request.

    Regards,

    Andrew.

    • 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