Skip to content
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

Updating readme.txt to include more description for various program's options #26

Open
student13371 opened this issue Nov 9, 2017 · 0 comments

Comments

@student13371
Copy link

What steps will reproduce the problem?

Using Update torrent - Insert new trackers list BEFORE or Append new trackers list AFTER and the following options are unclear for a novice user.

What is the expected output? What do you see instead?

readme.txt is very great in explaining 3 possible use case scenarios in updating .torrent file and the proper use of add_trackers.txt and remove_trackers.txt files.

However, readme.txt lacks the proper description of Insert new trackers list BEFORE or Append new trackers list AFTER and the following options behavior.

What version of the product are you using? On what operating system?

v1.32.0 stable. Windows 7 Ultimate.

Please provide any additional information below.

I've used Insert new trackers list BEFORE feature to insert a desired tracker A into beginning of trackers list of all my .torrent files. However, in some .torrent files tracker A didn't end up in the beginning, but was placed on lower positions. Probably because those .torrent files already had tracker A before insertion.

Updating readme.txt file to include what-to-do scenarios (as in the case of using add_trackers.txt and remove_trackers.txt), such as what options to use if user wants to keep original unique trackers and their order per each .torrent file while additionally adding new trackers in the beginning of a newly formed tracker list (in case there are duplicates in a newly formed tracker list remove the duplicated tracker that is below in the order and keep the one that is above).

Otherwise, this program is really awesome.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant