Making a particular layer of a cellview(layout) invisible in toplevel

Discussion in 'Cadence' started by suresh j, Jul 17, 2003.

  1. suresh j

    suresh j Guest

    Hi,

    In virtuoso layout editor I want to have some text in the corner of
    every cell view (cell1) having details about the owner, notes etc.

    I want this to be invisible if this cellview (cell1) is instantiated to
    some other cellview ( cell2 ).

    ie, If you open cell1 the text should be visible. But if you open cell2
    inside which cell1 has been instantiated the text should not be visible.

    Any help wd be much appreciated,

    thnx.
    suresh
     
    suresh j, Jul 17, 2003
    #1
    1. Advertisements

  2. suresh j

    Rajeswaran M Guest

    I dont think it is possible directly.

    My suggestions are,

    1) Add the layout properties which are the required informations in
    the cell1.

    2) Write a skill wrapper, binded to key, which will create the temp.
    hilite layers to show the information, with out opening the cell in
    edit mode.


    Or there could be some obviouse feautures with ROD objects?


    rgds,
    Rajes
     
    Rajeswaran M, Jul 17, 2003
    #2
    1. Advertisements

  3. Suresh,

    If "cell1" and "cell2" are in 2 different libraries,
    there are possibilities :

    Let say you have a library of leaf-cells "mylib1" containing all
    the cells comparables to the "cell1", then you have to make visible
    the layer on which are the "tag" labels.

    techDisplays(
    ;( LayerName Purpose Packet Vis Sel Con2ChgLy DrgEnbl Valid )
    ( myText drawing activeDrawing t t t t t )

    The other library "mylib2" which contain the macro cells (cell2)
    and the topcell of your design should have a techfile compiled where
    the layer is made invisible by default, you can also make it outside
    the LSW, with the "Valid" variable set to nil.

    techDisplays(
    ;( LayerName Purpose Packet Vis Sel Con2ChgLy DrgEnbl Valid )
    ( myText drawing activeDrawing nil t t t nil )

    The only drawback I see with this kind of workaround, is that you have
    two user libraries which use the same technology, but with different
    techfiles compiled.
    Also this method is not suitable if you want to attach your libraries
    to techlibs, otherwise you have to manage techlibs with different kind
    of displays.

    Hope this helps.
    ================================================================
    Kholdoun TORKI
    http://cmp.imag.fr
    ================================================================
     
    Kholdoun TORKI, Jul 18, 2003
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.