QuickAlign "center" to "edge-center" deprecated in Layout 6.1.7?

Hi Jorge,

I am assuming you're looking at old documentation, because if I hit the Help button from the F3 form it describes the fields that are on the form.

I suspect that maybe you just need to use the Right Mouse Button menu to control quick align. I just tried an align from the centre of one object to the edge centre of another object, and that worked OK. I did have "points and edges" enabled on the quick align mode - the right mouse button menu gives you the option to switch to edges only (and if that has been selected, the menu offers to switch you back to points and edges). My guess is that maybe you're in edges only mode?

Note you press right mouse button when you're in the Quick Align command to see the context menu.

Regards,

Andrew.

Hi Andrew, thanks so much for your prompt reply. I in fact thought initially it was the "Snap to edges" option being enabled, but I after checking again the problem persists. What's more, I really get fewer options than what described in the documentation (I checked the guide for version 6.1.7). Here is a snapshot of what I am getting:

As you can see, when I point to the edge center of the target object I get the yellow DOT and not the (small vertical yellow) LINE that would allow me to only align vertically both rectangles (and not to actually move the center of the origin object to the edge center point of the target object, as would happen in the example above).

Does this look maybe like a broken setup?

Thanks again for your help,

Jorge.

Oops! I guess the copy-and-paste of my snapshot didn't work (don't really know if its possible to add images here). If you don't mind, here is an external link to the image: 

http://s14.postimg.org/ex83gzkht/quickalign.jpg

Jorge,

You can upload pictures using the Insert/Edit media buttons in the rich text editor when posting - these are in the middle on the bottom row of buttons (between the right indent and the Paste from Word button).

Anyway, I think you can do what you want. Click the centre of the first object (which you've done) and then move slightly away from the edge centre and it should highlight the entire edge. Or, after clicking on the centre of the first object, do Right Mouse and change to edges only and then you'll only be able to select edges as the target. I think this was done to make it clearer whether the target is an edge - before it sort of showed you it as both a point and an edge, and it probably wasn't obvious which would win.

Ah, maybe I understand what you mean. I tried in IC616 and you could move slightly away from the edge and end up with a target alignment "edge" perpendicular to the actual edge. I'll add a picture (I'll have to edit the post because I'm writing this in a browser that doesn't reliably work with the insert media button - turns out it is currently not working in the other browser I was using too on my platform - so here's a link to the image instead) to show what it looks like in IC617 if I move away from the edge. Is this what you mean? I can't see how to do this in IC617 - I suspect something has broken.

Regards,

Andrew.

Exactly!!! That's what I am talking about! That small edge that would allow (whenever the point in the origin object is the centerpoint, I think) to align only in the X or Y dimensions, leaving the other unaffected. I guess then it is some kind of bug in IC617. Could you please also confirm if the F3-options and context menus that you get are like the ones I am seeing?

Thanks,

Jorge.

Hi Jorge,

Yes, the RMB menu and F3 options forms are as expected. They've been streamlined in IC617, and this is not a PDK-related issue. This doesn't appear to be anything to do with options on the forms - something has changed.

I can't find any record of this being reported as an issue, so I'm currently checking with R&D to see if this was an accidental change or if there's a hidden way of altering the behaviour.

Regards,

Andrew.

Hi Jorge,

Talking to R&D it does appear as if this is broken (I don't believe it was an intentional loss). We filed CCR 1537892 for this bug.

Regards,

Andrew.