search

ohio813 / bwhf

Automatically exported from code.google.com/p/bwhf
0 stars 0 forks source link

suggested feature #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
suggested trivial(but nice) feature: after scanning thousands of replays, 
it would be nice to be able to search (ctrl + F) the textbox that lists the 
hackers as to find the replay name of the hackers listed. my brood war 
charts has gotten so slow (due to excess replays) that it takes approx 20 
minutes to load, its not worth using as an archive searcher anymore.

Original issue reported on code.google.com by Hinson....@gmail.com on 6 Feb 2009 at 9:45

GoogleCodeExporter commented 9 years ago 
The tabs with a log text area also log to files. For example the manual scan 
tab logs  
everything that appears in its log text area to the file named manual_scan.log.

You can search in that file in every way you want to, and it's retained through 
BWHF 
Agent runs.

Yes, maybe it would be nice to search from BWHF Agent itself, so maybe we'll 
see this 
in future releases.

Original comment by icz...@gmail.com on 9 Feb 2009 at 5:54

GoogleCodeExporter commented 9 years ago

Original comment by icz...@gmail.com on 9 Feb 2009 at 5:54

GoogleCodeExporter commented 9 years ago 
Moreover by default the replays with hackers are flagged with a 'hack' tag in 
their 
name. They can easily be found with a search.

Original comment by icz...@gmail.com on 9 Feb 2009 at 9:35

GoogleCodeExporter commented 9 years ago 
Very nice work.
Maybe also another nice feature would be to remove that "-hack" from filenames 
from 
the recursive directory search. This would be useful when false positives such 
as 
latency changer are labeled as hack. This a very trivial feature completely up 
to you 
if you choose to handle this.
Further on latency changers (not just the one I use on east, others such as 
iccup and 
chaos #LL, #L1-L5), it might be wise to find spacing of MS for each game tick 
for 
each latency, such that you will never parse autogather for any latency 
changers. I 
don't know if you have already addressed this issue or not. Maybe its implicit 
in the 
fix you have already addressed.

Original comment by Hinson....@gmail.com on 9 Feb 2009 at 10:44

GoogleCodeExporter commented 9 years ago 
Its done. The new version (1.30) has these features.

Original comment by icz...@gmail.com on 18 Feb 2009 at 12:26