Change Folder Path (Os X 10.10.2 & Sync 2)

[lorccan]

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?

[GreatMarko]

Yes - under "My Devices", select your current device and change its status from "Connected" or "Synced" to "Disconnected".

 

You'll then be able to "connect" and specify the location of future incoming folders before they start syncing.

 

For example, a new folder added on machine A will then appear on machine B, but won't start syncing until you click "Connect" on it, and specify a location for the folder to sync to,

[tjluoma]

This is something _way_ too clunky. I ought to be able to move the folder in the Finder and BTSync should be able to recognize it from the information in the '.sync' folder.

[GreatMarko]

Provided Sync is running, you should be able to move/rename in your OS an existing folder you're syncing, and Sync will recognize the move/rename.

 

However, in the case of "moving", Sync might not recognize a move between different drives, only a move within the drive the folder currently resides on.

[lorccan]

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.

Edited March 4, 2015 by lorccan

[RomanZ]

@lorccan

Moving folder across volumes is more bound to filesystem limitations - it is not moved, it is copied - and old copy deleted. Therefore Sync can't track it (and scanning all drives is way too heavy operation). We are looking for ways to make it more easy and lightweight.

[lorccan]

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?

[GreatMarko]

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

 

 

You can!! See my first post.

[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?

[GreatMarko]

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?

 

It's the destination/receiving end - in your example, Machine B - that you'll need to set to "Disconnected" before adding your folder to A