Log automatic searches to system log

[LoRenZo]

One of the greatest features of the client is the automatic search based on the user's queue list.
I never really figured the activity in the background, and for that reason I would prefer sort of a text-based representation how this is being performed.
This could be perhaps optional, and logged in the system log in the first place for instance.
I think that in case this is ever going to be implemented, the best logged display would be something like this:

[date/time] searched for [filename] with identifier of [tth] on [amount] of hubs and found [amount] of new sources.

Since not all hubs allow searching by default, or some of them can have a too high search interval set (compared to the others) this could indicate if there are any hubs which the user is connected to.

[eMTee (realprogger)]

This is possible to make as an optional feature, however, it cannot be done the way it requested (all required data in one log event line) because due to the way searches work in DC, the required data are created by three different events in different times.
Since autosearches are performed no less than 2 minutes, in most cases logging from the different events can result a continuous block of log entries for a particular search.

A more complete solution would be to store and visualise the autosearch events and the autosearch queue in the GUI. This would be also useful to fulfill those earlier requests when they want the ability to see/modify the future queue of autosearches.