@Richard-18 said in Synchronisation - A batch of routes?:
I have a huge library of well over a thousand routes, which I have used and / or have gleaned up from elsewhere, simply to use perhaps at sometime or because I have shared them on another forum, to give people some possible ideas.
Although I would really appreciate folders being selectable for sync, as a go-in-between to just single routes or all routes, I think you should consider that my 300+ routes were synced completely in less then 50MB. So I am inclined to say that synced routes will not be in your way memory-wise. The idea of a complete sync is that, since there also is an in-app planner module, you can do whatever you can do online, also offline in your app.
@Richard-18 said in Synchronisation - A batch of routes?:
I am perfectly happy with being able to synchronise individual routes, one at time, which I do by making a copy and then synchronising the copy. These I put into a separate sub-folder, safe in the knowledge that the ‘original’ route from which the copy was made, will remain untouched. I guess it’s just the P thing in action again? It works for me, that’s all.
This method kind of defies the purpose of syncing. If you want to change a route without overwriting the existing one, you make a copy in your online library as well. Why not use the same method in the app?
But again, I think the idea of enabling syncing folder-wise would be a good idea too, although not completely by your argumentation