lorccan

I finally see what you mean. (I tried it when you first responded and it wouldn't work, but I had probably misunderstood.) Just to clarify, though: Machine A is to be the [initial] source, Machine B to be the [initial] destination. Are you saying that A or B should be disconnected before adding the folder to A?

Surely it can't be too difficult to have it as it was before: to allow the folder path to be edited locally ​before syncing starts?

It's not only clunky, but removes functionality that was previously available. If moving an existing folder between volumes worked, it might be just about OK, but in tests I found it just broke the link. What I did discover is that changing the default folder (in prefs) on the destination machine to the required volume before adding the folder at the origin allows the destination folder to be moved around but only on that volume with any certainty. [edit: I suppose that this is what the first answer was really referring to, but that we have different ways of explaining it only reinforces the clunkiness. It's not straightforward] I'd like the ability to either move the folder across local volumes or to allow explicit definition of the path.

When I add a folder to sync on machine A, its path on machine B is under the Default Folder Location. On the old version, I could choose different paths (and folder names) on each machine. Is this still possible?