• 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 lock the cell placement

Stats

  • Locked Locked
  • Replies 15
  • Subscribers 144
  • Views 23375
  • 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 lock the cell placement

bharath2k4er
bharath2k4er over 16 years ago

Hi, 

can someone help in locking the placement of the Instance (should not be able to move the instance once i lock the position) in the virtuoso layout editor using skill..

It is equvivalent to this command SET_OBJECT_FIXED_EDIT(GET_SELECTION) 1 (1 means postion fixed, 0 means postion is notfixed).This command is available in the IC compiler (ICC tool). 

 

Thanks for your support,

Bharath. 

  • Cancel
Parents
  • dmay
    dmay over 16 years ago

    My mistake. I defined the procedure after the call to the procedure. Simply move the call to leRegUserObjectSelectionFilter after the definition of the procedure.

    If you want to lock all of the instances for the set of code defined above, do the following:

    procedure(lockAllInsts(@optional (cv geGetEditCellView()))
        foreach(inst cv~>instances
            inst~>myFixedProperty = t
        )
    )

    Call this command to lock all the instances from being selected. Since this approach doesn't allow instances to be selected, there won't be an easy way to print a message indicating that the position is locked. You would have to create wrappers to the move or stretch commands, but this then becomes messy and difficult. I have tried this and actually opened the ticket with Cadence to get this selection filter. This filter made things much easier.

    If you want to unlock the instance, you'll need to change the "myFixedProperty" to nil. The following routine unlocks the selected instances.

    procedure(unlockInsts(@optional (insts setof(x selectedSet() x~>objType=="inst")))
        foreach(inst insts
            inst~>myFixedProperty = nil
        )
    )

    I did not intend this code I posted to do all you need it to do. It should serve as an example for you to work from. Take this time to get familiar with the Skill documentation, it is very good.

    -Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dmay
    dmay over 16 years ago

    My mistake. I defined the procedure after the call to the procedure. Simply move the call to leRegUserObjectSelectionFilter after the definition of the procedure.

    If you want to lock all of the instances for the set of code defined above, do the following:

    procedure(lockAllInsts(@optional (cv geGetEditCellView()))
        foreach(inst cv~>instances
            inst~>myFixedProperty = t
        )
    )

    Call this command to lock all the instances from being selected. Since this approach doesn't allow instances to be selected, there won't be an easy way to print a message indicating that the position is locked. You would have to create wrappers to the move or stretch commands, but this then becomes messy and difficult. I have tried this and actually opened the ticket with Cadence to get this selection filter. This filter made things much easier.

    If you want to unlock the instance, you'll need to change the "myFixedProperty" to nil. The following routine unlocks the selected instances.

    procedure(unlockInsts(@optional (insts setof(x selectedSet() x~>objType=="inst")))
        foreach(inst insts
            inst~>myFixedProperty = nil
        )
    )

    I did not intend this code I posted to do all you need it to do. It should serve as an example for you to work from. Take this time to get familiar with the Skill documentation, it is very good.

    -Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information