Details
-
Feature request
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Hi,
If you dont find this useful just ignore it,
but in my scenario, sometimes il add a 2TB+ transfer task on my main machine which goes to a network server, even over gigabit this takes a while.
Any task i ad after that (that have nothing to do with it) even smaller ones will be paused and will wait until the big one finishes.
because i like the 1 task at a time 99% of the time, would be cool if there was a button of a flag that you could apply to a specific task or all of them which makes the queue ignore that the task is already running and will keep going through the queue, or will process a new task when added before the first one finishes.
So it will have to basically not count that as a running task, so it doesnt delay the queue being processed.
Attachments
Issue Links
- relates to
-
CH-8 Skip "pending" state for task with minimal duration (sf.net)
-
- Open
-
I think there are such possibilities available already:
1. You can "Resume" the queued task and that will run it regardless of the queueing setting.
2. There is an option in settings (Limit maximum operations running simultaneously...) that lets you adjust count of tasks that can be run at the same time.
Is it what you wanted here?