Stats

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

add instance from library via pulldown menu.

flintae32
Hi IC Community

My experience with Cadence’s Skill is very limited. I have created a pull down menu with sliders in the upper layout editor banner window with some success. My question is, how do I utilize the callback function to place an instance from a cell library into the layout editor window, when selected.

software version: 5.1.41

Example below:

mlf_frame = hiCreatePulldownMenu( 'editMenu "edit"

list(

hiCreateMenuItem(

                           ?name `3x3

                           ?itemText "M_3X3"

                           ?callback  "??????()"

What command should I place here in the callback function ??????. Any help would be greatly

appreciated.

 
Thanks

Johnny
Parents

  • Hi Johnny,

    This is slightly tricky - if you don't want to have to enter the lib/cell/view in a form (as initiated by a call to leHiCreateInst() ) then you would need to call something like dbCreateInstByMasterName() - the problem is that this function needs a location (origin) to place the instance at.  I would use something like "enterPoint" or "enterPoints" to gather the instance location(s) and use the addPointProc to place the instance at the most recently provided coordinate (which would be something like car(last(pts)), assuming "pts" was the argument used for the addPointProc function).  The following is an approximation of what you need:

    
procedure(CCFeditMenuCB()
  enterPoints(?prompts list("Point at the location for the instance")
    ?addPointProc "CCFcreateInstAtPoint"
  )
)

procedure(CCFcreateInstAtPoint(win pts)
  dbCreateInstByMasterName(
    geGetEditCellView(win)
    <libNameHere>   ;; this is where you hard-code the library, cell and view names
    <cellNameHere>
    <viewNameHere>
    nil             ;; let the editor choose the instance name
    car(last(pts))
    "R0"            ;; hard-code orientation of R0
  )
)

    The name that you put in the edit menu item callback is "CCFeditMenuCB". Once you call this it starts a call to enterPoints that allows you to place one or more instances, and when you are doing you just hit the Escape key.

    I hope that this helps you.

    Regards,

    Lawrence.

Reply

  • Hi Johnny,

    This is slightly tricky - if you don't want to have to enter the lib/cell/view in a form (as initiated by a call to leHiCreateInst() ) then you would need to call something like dbCreateInstByMasterName() - the problem is that this function needs a location (origin) to place the instance at.  I would use something like "enterPoint" or "enterPoints" to gather the instance location(s) and use the addPointProc to place the instance at the most recently provided coordinate (which would be something like car(last(pts)), assuming "pts" was the argument used for the addPointProc function).  The following is an approximation of what you need:

    
procedure(CCFeditMenuCB()
  enterPoints(?prompts list("Point at the location for the instance")
    ?addPointProc "CCFcreateInstAtPoint"
  )
)

procedure(CCFcreateInstAtPoint(win pts)
  dbCreateInstByMasterName(
    geGetEditCellView(win)
    <libNameHere>   ;; this is where you hard-code the library, cell and view names
    <cellNameHere>
    <viewNameHere>
    nil             ;; let the editor choose the instance name
    car(last(pts))
    "R0"            ;; hard-code orientation of R0
  )
)

    The name that you put in the edit menu item callback is "CCFeditMenuCB". Once you call this it starts a call to enterPoints that allows you to place one or more instances, and when you are doing you just hit the Escape key.

    I hope that this helps you.

    Regards,

    Lawrence.

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.