-
Notifications
You must be signed in to change notification settings - Fork 667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature|Usability] The sync client's "sync folder info" always "resets" #367
Comments
Completely agree that a historical look on this tab would be useful. Maybe a second column that shows what has been done in the last "select log window (1 hr-1week") amount of time, and then also a column for the last sync. I know the idea of a user viewable ownCloud activity log is also on the short list, which could be the source of some of this data. |
I would not even ask for something as advanced as a historical look, just a normal senible view would be enough for me. ;-) |
Solution would be something like "when all reported values are 0, keep showing the previous one", right? |
The feature of a "historical" view of syncs has landed in master. |
Hey everyone,
whenever the client does a successful sync, the "sync folder info" displays what has been done in this sync. If something was actually sync'd (read: non-overhead data was actually moved through the network), this is what I want to know, that's nice.
BUT most of the time (every 30s or so), nothing really happens because all data is already up to date. In consequence, the info stubbornly shows "0" everywhere. That is true but very weird, because what every user wants to know is either a) what's being done right now or b) what has been done, the last time something was actually done. Y'all know, what I mean?
Example:
If in the last 20 hours nothing has changed on any side and therefore nothing has been synced, I want to know, what the client did 20h and 1 minute ago, right? Or if it is currently syncing, what is being synced right now?
Greetings and thx
Laryllian
The text was updated successfully, but these errors were encountered: