XDCCCatcher.net

The GUI of catcher is pretty much unusable for me. Am I missing something? After using any search query, the program sends an auto refresh command, however the auto refresh is not based on the search query and uses all the packets. So essentially it just shows all the packets instead of my search.

[11:22:37] [Tmainform.RefreshFilterTimer]-Sending filter refresh
[11:23:07] [Tmainform.RefreshFilterTimer]-Sending filter refresh
[11:23:37] [Tmainform.RefreshFilterTimer]-Sending filter refresh
[11:24:07] [Tmainform.RefreshFilterTimer]-Sending filter refresh

Also I have tried 64 and 32 bit versions on 3.0.0.12 and on multiple computers (Windows 10, Windows Server 2008 R2) with same results.

Did you modify the search filter after you clicked on 'search' ?
The autorefresh will use the filter param as they were when you click on search. When you make any changes after this, you'll have to restart the search. I'm still thinking about a better way to implement this.

No, it does it without modifying anything. If I search and sit there for 5-10 seconds, I get every packet in memory displayed like I didn't even do a search. I have had this issue with the new version since it was released.

?

i'm going through the searchfilter code to find what might be causing this.

So if i understood correctly, you entered the search filter and clicked on 'filter' and all of the packs just kept on being displayed?

Can you see if after a resfresh, the correct filter is applied?

So, you changed the filter parameters and you click on the big 'Filter' button correct?
Only when you click on that button, the filter will be updated and refreshed.

When you wanted filtering, at the top it said "Filter (enabled)" ?

I did finally figure out what the problem is, when I have a filter enabled (a search) everything looks good but as soon as catcher finds another packet post, it gets added to the filter list. This packet gets added even though it doesn't match the filter criteria.

Thanks for reporting. Can you just let me know which filtering was enabled?
I'm currently testing the filtering on bots and can't simulate this particular issue.
Was the filter enabled using a 'Search on Bot', 'Channel' or 'Network' as i just fixed an issue there with the autorefresh.

Thanks!