• 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 Design
  3. Controling Opus Objects Window

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 14222
  • 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

Controling Opus Objects Window

RDRamirez
RDRamirez over 11 years ago
These commands are from the Virtuoso command window:

_pteHiObjectSetExpanded(dwindow('pteObjectPalette1) "Blockages" nil)


_pteHiObjectSetExpanded(dwindow('pteObjectPalette1) "Blockages" nil)

How and where can I put these commands?

Thank you,

Roger
  • Cancel
  • RDRamirez
    RDRamirez over 11 years ago

     For some reason some extra stuff got added to this question. Ignore the stuff above the

    _ptehiObjectSetExpand .... commands

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Marc Heise
    Marc Heise over 11 years ago

     Hi,

     

    the underscore as the first char of a functions means "private". Thats an undocumented Cadence internal SKILL function which  might be changed without notice. We not want our customers to use these. The function you mention is probably about Layer Palete manipulation.

    What is the underlying problem of your question? What are you trying to achieve? 

     Kind regards,

    Marc

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RDRamirez
    RDRamirez over 11 years ago

    The Object menu on the left side of the OPUS window has +Shapes, +Boundaries, +Soft Blocks and +Blockages. When I use that menu to V (visual) or S (select), I don't want to shroll down the long list of items. The "nil" at the end of the commands compresses the menu items.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Roger,

    Not sure which version you are using, but in IC616 there are two public functions, pteExpand() and pteCollapse(). In fact the private function you reference doesn't exist any more (which shows the danger of using a private function). So for example you can use:

    pteExpand("Boundaries" "Objects")

    or pteCollapse() with the same arguments. That said, everything shows up collapsed by default anyway, so not sure you even need this?

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RDRamirez
    RDRamirez over 11 years ago

    Cypress Semiconductor in San Jose, CA are using:

    sub-version  IC6.1.5.500.9  (32-bit addresses)

     Is this placed in the .cdsinit file?

     I'll try it.

    Thanks, Roger

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Roger,

    The functions I mentioned are new in IC616 - I just checked. Also, in IC616 the behaviour has been changed so that the palette items are collapsed by default anyway.

    I just wrote some code which enables this in IC615, but uses some private functions and so I have encrypted it and added some checks so that it doesn't do anything in IC616 - other than print a warning that it is redundant.

    To use the attached file, use:

    load("~/skill/abCollapseAllObjects.ile" "1036035")
    abRegAutoCollapseObjectsOnOpen()

    Of course, change the path in the load function to where you've installed the file. The second argument must remain as it is a password for the encryption.

    Having done this, any time you open a layout window, it will attempt to collapse the items in the objects palette. It doesn't do it when you push or pop the layout window - the assumption is that if you've expanded it, you want to stay expanded in that window.

    Regards,

    Andrew.

    abCollapseAllObjects.tar.gz
    • 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