-
Notifications
You must be signed in to change notification settings - Fork 26
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 Request #145
Comments
If you are currently sharing a file, it should appear with a checkmark in the search results. If you are no longer sharing the file, MuWire forgets about it completely. It is not practical to remember every file that has ever been shared or downloaded as the database would grow without limits. Regarding keyboard shortcuts, see this forum thread. It would be nice to have those configurable but I can't say when it can happen. |
What I can do is a "blacklist file" feature where you can say that you never want to see a result for a given hash, regardless whether you've downloaded a file before. That should achieve what you want, no? |
Is there a log level where I can get the information I want: |
No, I can add one. |
That would be nice. Thank you. |
See the commit referenced above |
It works. Thank you very much! |
Some ideas:
so that it is readable by other tools.
Give each file an attribute if it was downloaded complete, cancelled, was shared earlier by me but not right now, ....
Add some Icons in search results that indicate attributes from above.
This will help a lot to NOT to download files again that I have downloaded some time ago.
Right now there is only a Icon in search results that indicates that I download this file right now.
Add a Dialog "Are you shure?" when cancelling files, with an option to turn this dialog on/off in configuration settings.
Add Keyboard-hotkeys for the toolbar button catogories (_S_earches, _D_ownloads,...) to easily switch the
categories. Make the shurtcuts fully configurable, bec. of potential problems with several
Windowmanagers/Desktops that use the same shortcuts.
Thank you.
The text was updated successfully, but these errors were encountered: