How to keep some instances un-movable (fixed position) in virtuso

In IC615 (you didn't say which version you are using, and it's rather useful to know...) you can use Edit->Select->Set Selection Protection to "protect" a number of shapes/instances. This will make those objects unselectable (you can highlight them from the same menu, or temporarily override the protection, or remove the protection). That means you won't be able to accidentally select them and hence not be able to move them.

In earlier releases, you can use my SKILL code as described in this article on Cadence Online Support to do the same thing.

If you're using VLS XL you can also use the constraint manager to add a "locked" constraint on the instance to stop you being able to move it when in Constraint Aware Editing mode. Could also use a "fixed" constraint.

In IC5141 it's also possible using Virtuoso Layout XL - you have to use Tools->Constraint Manager in the CIW, and then you can add a "fixed" constraint for some instance. You have to turn on "Constraint Assisted Move and Stretch" in the Layout XL Options form too.

Regards,

Andrew

 Dear Andrew,

Thanks alot for your reply.

I am using IC5141. I tried Tool ->Constraint Manager in the CIW.

But couldn't figure out how to 1) Select a instance to be added to the manager

                                          2) To make the instance Fixed

Could you please tell how it can be done.

Kind Regards,

 Dear Andrew,

I also tried with your SKILL code.

Itis working fine.

But,  I  protected  A,B,C

Then  I want to unprtect only C , then what I should do.

 Dear Andrew,

I got. I think I should have selected Create, Then add the instances in the 'Fixed" option.

With that, I am able to keep them fixed in the layout but they are selectable unlike your SKILL code.

Kind Regards,

 If using my SKILL code, you have two choices:

1. Use CCSprotect->selectProtected() , then deselect those you want to keep protected, and then CCSprotect->unprotectSelected()
2. Use CCSprotect->setOption('protectMode nil) then select the one you want, do CCSprotect->unprotectSelected(), and CCSprotect->setOption('protectMode t) to turn protection back on again.

Obviously this tends to be easier if you have things defined on bindkeys. You could also define a bindkey to be:

CCSprotect->setOption('protectMode !(CCSprotect->getOption('protectMode)))

which will toggle protect mode on or off each time you press it.

In the IC615 implementation, there's the option to unprotect an object post-selection, so you can click on it regardless of whether it is selectable (I didn't add that in my code, but it wouldn't be too difficult with an enterFunction).

Regards,

Andrew.

 Dear Andrew,

Thanks a lot for your reply.

I like to do some modification to your skill code.

But the "SKILL" is a new language to me.

I want to know the meaning of each standard function present in thye code.

I went through  "Cadence Analog Design Environment SKILL Language Reference", but I could not find the many functions present in your code.

Could you please point to some document/source from where I can get the meaning of all the STANDARD functions you have written in the code.

Kind Regards,

Given that this code is for the layout editor, it's hardly surprising that nothing is covered in the Cadence Analog Design Environment SKILL Language Reference.

There are functions from three groups in this code:

• Cadence SKILL Language Reference (worth reading the User Guide too). The code is written using the SKILL++ lexical scoping capabilities, which provides the ability to create local functions - in this case it's written as a package which exports a number of functions, whilst keeping some functions and some data private.
• Virtuoso Design Environment SKILL Reference (for the ge (Graphics Editor) and db (Database) functions used in the code)
• Virtuoso Layout Suite SKILL Reference (this is in fact just for the leRegUserObjectSelectionFilter function)

The code is written using LISP style (SKILL also allows you to use a C-style which is probably more common, but I tend to write most of my code using LISP style; the language is really a LISP flavour underneath, but it makes no difference to efficiency or speed which style you choose).

Hope that helps!

Kind Regards,

Andrew.

 Dear Andrew,

Sorry, I think I have searched  the functions in the wrong reference.

Thanks a lot. I will dig into the documents to understand the functions.

Kind Regards,