Comment 15 for bug 1771424

@Art
I'm not a KiCad developer, at least not at the moment, so you don't have to be afraid I could affect others so that the bug wouldn't be fixed. Maybe I should have made it clear from the beginning. I only noticed this bug report and I had experienced partially same problems with these dialogs. I wanted to share it.

I'm also sorry about not being more clear about my focus which was about moving items, not about rotating. Maybe that's why you don't understand what I'm saying. Rotating needs only one point. However, moving an item relative to other than its original location needs two reference points even if you don't feel you need them.

The first one is the "Move Relative To" position in the "Move Exactly" dialog. The second one is the center point of the selection or some other point in the selection. If there weren't any such point, you couldn't give any meaningful interpretation to the "Move vectors". Only if you move an item relative to its current position you don't need reference points because you can think about length and angle (a vector) instead of location. But the other options, "User origin", "Grid origin" etc. require a location instead of just a vector. And you can't put e.g. a rectangle into an x,y location unless you first know which point of the rectangle should be in that location. What these options logically do is putting the selected item into some coordinates instead of just moving it along a line (vector).

I'm sorry I can't express myself more clearly, but that's not the point (and sorry about the pun, too...). I'm sure the developers can see your point and mine.

About the cursor - I know very well how it works because I carefully tested it before a wrote my comment. If you select Full window crosshair and Always display crosshairs in Display Options and then choose a grid value large enough (or zoom close enough) you can very clearly see how the KiCad crosshair cursor snaps to the grid while the mouse arrow cursor doesn't. It's also reflected in the X and Y values in the bottom of the window. And what's more, this (X,Y) location stays the same after the context menu is opened and the mouse cursor is moved. Selecting something doesn't affect this.

At least in Linux, latest KiCad source code from git, with the Modern Accelerated toolset.

Unfortunately I couldn't get the video playing, maybe it's my Linux system. Probably it would have helped me to understand what you meant.