Layout 2020 NOT Referencing Existing Geometry During Move/Copy - Why!?

LayOut
1

I keep finding annoying things in Layout 2020 that are either not fixed or actually working worse. For example, you seem to no longer be able to copy an object and snap to the original geometry. This means that you cannot do things like make 5 evenly spaced copies of a square (by typing *5 after copy) without having at least 2 copies of an object to start with.

x
x1286×214 3.79 MB

I read somewhere (can’t find it now) that LO2020 implemented new graphics handling to improve performance and I suspect this is a result of that.

2 Likes
2

It looks like you are relying on grid snapping. Do you have the same interval set in both?

This is in LO2020 using exactly the same move/copy method I’d have done in 2019 or 2018 or…

copy
copy819×493 75.5 KB

1 Like
3

Don’t know how you’re able to do that Dave.

Like I posted on another thread, I’m having this problem too…

snapping_02
snapping_021638×696 661 KB

I’m on version 20.2.172 and it was installed correctly :slightly_smiling_face:

1 Like
4

Dave,

Nope. Not using grid snapping.

5

I wasn’t either. Did you try doing what I show?

6

Paul, it looks like you have Object Snap turned off. It needs to be turned on for what I showed.

7

Try it? I showed exactly the issue in the first post.

8

Object snapping is on…

1 Like
9

That’s odd.

10

I swear the Release notes mentioned that when you drag something the graphics handling is different in 2020. something to do with that Layout will not try to render the complete geometry as you drag.

11

And also there’s this difference that suggests the elements during drag are representations of the objects rather than true copies of the objects themselves.

z
z1098×418 2.04 MB

1 Like
12

The graphics handling is different in 2020.2. It’s designed so that the display doesn’t have to keep re-writing as things are moved.
copy

13

I’m not sure how Dave is getting it to work correctly. With 20.2 on Mac and Windows, I get the same behavior you’re seeing. Here is a screen recording of the behavior in Windows. Note that the duplicated object does snap to other existing objects, but not to the one you started from.

I wasn’t able to find an existing issue about this, but I have reason to believe the behavior will be back to normal in some amount of time from now.

2 Likes
14

Evidently I’m doing it wrong. It works fine for me, though, so I’ll keep doing it wrong.

1 Like
15

How long is…

:wink:

16

And just to cover all bases… same behavior when you modify the reference point BEFORE move/coffee…

y

1 Like
17

It must be the way you are holding your tongue :stuck_out_tongue:

1 Like
18

That might be.

1 Like
19

Snapping to original geometry in copy move is broken for me too in LO2020. I have no idea how DaveR makes it work, the SU gods favor him.

My lame workaround for arrays is to draw a line to snap to first.

4
41005×640 168 KB

1 Like
20

Cmd C, Cmd V should work, too…:wink: