Moving folders within Grive

[Chalgafe]

Whenever you move one folder into another in Grive, it won't just move it into the other folder. what it will do is the following. The Folder will copy all of the files within the folder to the other folder in the app. in google drive at the webs it is uploading all of the files again by uploading them to a new folder instead of just moving them. For example, lets say you have "A" folder and you want to move it and its contents to folder "B". However, when you move folder a into B, you are not moving it within the drive, it is not assuming you are moving but rather assuming you just uploaded new files and deleted the old one. While synchronising, you have 2 "A" folders one in its original location and one in the B folder which is slowly reuploading all of the contents from your local grive folder to the Google drive on the webs. It would be way more effective and faster if Grive scanned changes or new locations within the grive folder and applying it on the google drive instead of just uploading and deleting files just to leave the drive as the folder. That is the only issue, everything else is great! People like you make Ubuntu worth it. it is not the value we get from our money,like microsoft, but the community that helps each other. hugs

[Chalgafe]

If the issue is not well explained, tell me

[estomagado]

Trying to make it simple: suppose you move files from one subdir to another subdir, both inside your LOCAL Grive folder. When you call Grive to sync the files, it tells Google Drive to first delete the files in the original location and then upload the files, from local to the new location on the cloud, again. It would be more simple and save time and bandwidth if you just tell Google Drive: "hey, man, move files there on the cloud, will ya?". Grive would not have to upload all files again, just send a command to tell Google Drive to manage things there. A quick glance at Google Drive API tells me this is possible. In fact, it's what the official client does.