Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Inheriting Torrent Settings #9939
Let me to introduce "Inheriting Torrent Settings" feature.
From a user perspective, it is a set of torrent settings (like Save path, Ratio limit, etc.) that have some default values and can be overridden at different levels (e.g. at Category level or Torrent level).
From a developer perspective, it is a set of torrent settings that is bound to each "manageable item" (Application, Category, Torrent).
A value for "Save path" setting of "Torrent A" is not set so it inherits the value from its parent item (Category "Misc"). Category "Misc" also hasn't explicit value of "Save path" and it inherits the value of its parent item (Application default "Save path" setting). So the effective value of "Torrent A" "Save path" setting is "C:\Users\John\Downloads".
Inheritance of Setting works in two ways:
Each setting is mapped to a policy that determines how this setting will be created. There is also a default policy that allows you to not explicitly set all policies.
I want to pre-discuss this feature here and get the main approval before proceeding with its implementation. So waiting for your comments (I'm more interested in the comments of team members, but users can also speak out if someone has something really valuable).
You misunderstood me. They're just handle the Torrent Settings but don't use themselves. See my example carefully.
Tomorrow I will add an example of their work.
referenced this issue
Dec 9, 2018
Is this what's necessary to implement separate max connection limits for downloading and seeding torrents? Found here: