Yes any change in sorting will completely recreate the table so that the overall total always is placed at the bottom regardless of column sorted on.
And yes, by design can not run dry-run on multiple searches on the same target files as each pass through the files will mess up the previous searches calculated match positions, changes potential match context, and would miss matches that are built up from earlier replacements.
So a dry-run table must represent a single search over the set of target files.
Quote:
Originally Posted by Mister L
This is brilliant. 
Question: in the "Counts Report", if I click on the header to modify the sort order, it seems to restart the entire count. Is that expected? It's not necessarily a problem, I am not sure I would really need to modify the sort order often / ever, just thought I would mention it just in case.
Other question, the dry run does not seem to be compatible with (multiple) groups of saved searches, is this intended? I am not sure if it's a bug or just that the dry run is only meant to be used for one search at a time, which would be reasonable.
This is what I mean:
|