-
Notifications
You must be signed in to change notification settings - Fork 4
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: Pieces Bar for availability and each file #33
Comments
Sadly, this cannot be done without extra work in Transmission itself as there is no information about piece-to-file mapping exposed via the RPC. The daemon must know this because it must be able to map incoming pieces into corresponding files, so this is "just" a matter of exposing this mapping. |
PR submitted in Transmission : transmission/transmission#5578 |
As discussed in transmission/transmission#5578, the piece-to-file mapping can be deduced directly from the ordered list of files, their lengths and the piece size, all of which are already available via RPC. There is no need to extend the Transmission RPC interface. In fact it would probably make more sense for your software to manually compute the mapping despite the new fields, because that way it would work even with older Transmission versions. |
Agreed - |
transmission-remote-gui#1454
I like the idea, sounds cool and will be interesting to see how the code drawing the main piece bar does it and whether it's reusable in the VarGrid used for files.
The text was updated successfully, but these errors were encountered: