@Brian-McG said in Synchronisation - A batch of routes?:
Hi @Richard-18 thats sounds like quite a bit of work you have been doing copying & renaming
@Richard-18 said in Synchronisation - A batch of routes?:
I do not want to synchronise my entire library, as I’d much rather leave the library of ‘original’ routes intact and unaltered.
My question is what do you think is going to change with your library?
All the sync does is make the same file available on both the web site & in the mobile app
As far as I understand there will be no change to the original file / route
I believe the whole purpose of sync was to help stop all the copying / downloading of files / routes
Not so, I’m afraid. At least as far as I can tell in my experiments, practicing to see how it all works.
If an ‘original’ route, for instance one that I hold in my library, is synchronised with and then amended in the app (say for example by shortening or extending theroute) the changes will be synchronised back to the original.
That is, I guess, one of the purposes behind synchronisation: That changes made elsewhere will be synchronised and made binding elsewhere.
See example below, please.