linuxdcpp-team team mailing list archive
-
linuxdcpp-team team
-
Mailing list archive
-
Message #06776
[Bug 1153265] Re: Manual search related issues and feature requests
I numbered your reports to be able to reflect them. (Next time it's
easier to just report these separately)
#1 is reproducible, here's the result of the quick discussion
<poy> i think it's usable enough for the moment, even on big hubs. It's usable enough to afford real-time display rather than delaying and searches are a requested action (unlike user lists & transfers) so the user can understand if it lags some there.
#2 your idea can be a solution but also, selection using a hubgroup
dropdown would also add a great improvement of usability there
#3 is a deficiency of the NMDC protocol, there's no solution for it and
also it doesn't happen to ADC. http://dcpp.wordpress.com/?s=nmdc+search
gives you technicals behind this deficiency. Also please get yourself
updated about how searches work on DC++ and why they cannot be
'cancelled'; it's described in the first part of
http://dcplusplus.sourceforge.net/webhelp/window_search.html - So this
is an Invalid request.
#4 good idea and I guess it can easily be done
** Changed in: dcplusplus
Status: New => Confirmed
** Changed in: dcplusplus
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/1153265
Title:
Manual search related issues and feature requests
Status in DC++:
Confirmed
Bug description:
Manual search related issues and feature requests
Please find my issues and improvement related suggestions for manual
searching below:
#1 - When searching for keywords that generates a considerably large number of results in small amount of time then the client often gets unresponsible as long as the results added to the list in the Search window.
I assume the reason for this is that it uses the main thread as well.
I would like to ask for creating a seperate thread for searching too.
#2 - Including/excluding hubs from search can only be done by adding/removing the wanted/unwanted hubs one by one using the checkboxes. Although is it possible to select multiple hubs, pressing "space" only marks/unmarks only one hub, not all the selected.
I would like request to get this fixed, i.e. "space" marks/unmarks all the selected hubs.
As a reference, connecting to multiple hubs from the favorites list for instance can be done when selected them and pressing "enter".
#3 - At the time when the first search is being evaluated, the result
is only being gathered from the corresponding hub(s). Performing the
SAME search for different hubs results in including the hubs from the
previous searches, even when using a different search window after
closing the last involved one. It seems that the previously
"cancelled" searches are not actually being terminated. The individual
searches should only include results sent from the hubs that are
marked for the related activity.
#4 - Currently, there is no way to perform a "quick search" for the individual hubs. If someone wants to do a search on a specific hub, they need to select the hub manually from the list.
I would like to request a feature that implies a context menu on the hub's window (just like "copy address to clipboard" and "reconnect") which should be named something like "search on this hub" and upon clicking on it, a search window would pop up with only the current hub being marked for the results.
I can understand that not everything might be impletementable - at
least for the time being -, but I would like to see at least some
parts of the list being adjusted accordingly in the very next
releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/1153265/+subscriptions
References