You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.
Feature description
In my workflow, I often work with large folders that I prefer to keep paused from syncing to reduce CPU usage and conserve battery life. Continuous automatic syncing of these large folders can lead to excessive resource consumption, especially on mobile devices or laptops. However, there are times when I need to sync these folders manually to push or pull updates from the server.
Currently, the only way to sync a paused folder is to resume syncing entirely, which then requires me to manually pause it again after the sync is complete. This process is time-consuming and prone to errors if I forget to re-pause the folder.
I would like a feature that allows me to manually sync a paused folder without having to change its overall sync status. This would give me more control over when large folders sync, while still maintaining the benefits of a paused state for most of the time.
Proposed solution
Introduce a "Manual sync once" option for paused folders. This would allow users to manually trigger a one-time sync for a specific folder without changing its paused state.
User Interface: When right-clicking on a paused folder, there should be a new option called "Manual sync once" (maybe called "Manual sync now") in the context menu, as shown in the attached image. This option would be located above the "Resume sync" option.
Behavior: When "Manual sync once" is selected, the paused folder would perform a single sync operation with the server and then automatically return to its paused state after the sync is completed.
This feature would allow users to maintain a paused state for large folders, conserving resources, while still giving them the ability to manually sync when needed.
Alternative solutions you considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Pre-submission Checks
Feature description
In my workflow, I often work with large folders that I prefer to keep paused from syncing to reduce CPU usage and conserve battery life. Continuous automatic syncing of these large folders can lead to excessive resource consumption, especially on mobile devices or laptops. However, there are times when I need to sync these folders manually to push or pull updates from the server.
Currently, the only way to sync a paused folder is to resume syncing entirely, which then requires me to manually pause it again after the sync is complete. This process is time-consuming and prone to errors if I forget to re-pause the folder.
I would like a feature that allows me to manually sync a paused folder without having to change its overall sync status. This would give me more control over when large folders sync, while still maintaining the benefits of a paused state for most of the time.
Proposed solution
Introduce a "Manual sync once" option for paused folders. This would allow users to manually trigger a one-time sync for a specific folder without changing its paused state.
User Interface: When right-clicking on a paused folder, there should be a new option called "Manual sync once" (maybe called "Manual sync now") in the context menu, as shown in the attached image. This option would be located above the "Resume sync" option.
Behavior: When "Manual sync once" is selected, the paused folder would perform a single sync operation with the server and then automatically return to its paused state after the sync is completed.
This feature would allow users to maintain a paused state for large folders, conserving resources, while still giving them the ability to manually sync when needed.
Alternative solutions you considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: