Stats

  • Locked Locked
  • Replies 20
  • Subscribers 145
  • Views 21553
  • 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

Asking SKILL Code for Virtouso

archive

I'm new to the forums and really need this code.

Here goes, I would like a SKILL code for Virtouso that goes something like this. It's a "Flip Command". The code should flip any object-->instance, path/wire, polygons, rectangle, contacts etc. either "vertical" or "horizontal". And added to that, if you select multiple objects, you could also flip them "vertical or horizontal". it's like a picture when you flip it or mirror it.

like, the objects are selected, "123" when FLIPPED all objects becomes "321".

Thanks. I hope someone could help me, i have other request for Virtouso but they don't have any forums.


Originally posted in cdnusers.org by wonderkamote

  • The link to the file in the previous posting in this thread is now working - IT fixed it.

    Best Regards,

    Andrew.

  • Hi Andrew.  I believe this code does exactly what I need, but when I load the file and try to use the command CCSflip(), I get the below error message.  Is there something else I need to set?

    *Error* eval: undefined function - CCSfindBBox

     I used your example to load the CCSflip.il file and set it to a particular bindKey.

     Any pointers would be much appreciated.

     Thanks in advance,

    Janet

  • Janet,

    It seems that the previous attachment I uploaded a couple of years ago was incomplete. Try this one instead.

    Andrew.

    CCSflip.il

  • Awesome - works like a charm.  Thank you very much for your quick response!

  • Hi Andrew, For me it's not working as it should, e.g. if MX flip (F1 key assigned) is ok, then MY (F3) is not working ok, there is some offset, so the object is not flipped in place and when I rotate the same object for 90 deg with move and right mouse click, then MY is ok but MX it's not? 10x

  • What you're describing is not very clear. It would help if you said exactly what function arguments you're using in your bindkeys, and showed some pictures (you can attach a picture using the Options tab on the forum) to illustrate the problem.

    Andrew.

  • Ok, I'll try to explain better now. I've assigned CCSflip() to the F1 key, and CCSflip(?orient 'MX) to the F3 in a my "BINDKEYS" file. When I place instance in the layout (eg 0.0 coords) with R0 original rotation (1st pic in pic) and hit F1 key instance is flipped and shifted to the left (2nd pic in pic). If I hit F3 (from org position - R0) then it's ok flipped in place without shifting(3d pip) Similar goes if instance is placed with R90 (4th pip) but this time F1 is working ok (5th pip), but F3 not (6th pip). It seems that somehow transform coordinate is not well calculated whether the instance is not symmetric? Thanx

  • Since the code simply uses the bBox attribute of the instance, it would suggest that the bounding box extends differently to the left and right of the instance. If you have the instance placed at the origin, maybe you can give a picture with the instance at full depth, and with the stop level set to 0 (on the Display Options form) so you see the outline of the instance? My guess is that the bBox (which you can check with car(geGetSelSet())~>bBox if you have the instance selected) is aligned with the visible shapes vertically, but not horizontally.

    Regards,

    Andrew.

  • You were right, component bbox and origin are different. BR

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.