@SpectateSwamp said:
The initial reason behind the merge was that the directory lookup was so slow. To just find all the txt files on C drive took a minute or more. So instead. I created a Merge. Any good search needs a merge/append. The start and end of each file is in the combined file. So when search finds a match. I know which file it came from and display it in the form border. The file name is generally useless, unless your are searching source code.
I find this as a very interesting insight into how you program.
I'm familiar with directory searches in code, done quite a few myself (vb6 as well as C++). And when there were problems with performance, it was always (ALWAYS) something I did. Such as appending to a string inside a for loop (so that it got created and copied with every loop). When I realized those mistakes and made the appropriate changes, performance wasn't an issue.
But instead of looking at how to make your code better (a basic premise of Open Source) you just decided to duct-tape together some solution to make it work right there. And I'm using the work 'work' very loosely, as in 'meets the requirements' with no understanding of how good (or in this case, bad) the requirements were. -- General difference between "programming" and "developing" software