Word wrapping is expensive, especially when trying to display a lot of contents. To see a list of valid command line parameters go to the "Help->Command Line Parameters" dialog (or run FileLocatorPro.exe -h).
Filelocator pro sadeempc pro#
There is even an option to switch off the GUI (Graphical User Interface) and save the results directly to a file, useful when integrating FileLocator Pro with other applications. You can specify the initial values for FileLocator Pro through command line parameters. Specifying default values via the command line Note: Make sure that FileLocator Pro is associated with SRF files in the Shell Integration settings. Then when you open the shortcut FileLocator Pro will start up with your most common search options. Save your most common search criteria as a SRF file and put a shortcut to the file on the Start menu.
Filelocator pro sadeempc windows#
For example, while browsing files and folders in Windows Explorer you can launch FileLocator Pro by right-clicking on the folder and selecting FileLocator Pro from the folder's context menu or using the short-cut key combination Ctrl+F. Launching FileLocator Pro from Windows ExplorerįileLocator Pro can be integrated with the Windows Shell through the Shell Extensions settings. Would match all folders called "release" two levels down from the "c:\usr\dev" folder. The expression is not processed on the whole path but on the path parts, e.g. In the 'Look In' field separate each folder with a semi-colon e.g.Įxpressions are supported on folder paths, to use the feature use the expression drop down list next to the Look In edit field. For example, you can search everything but COM and EXE files by setting the file name to the Wildcard Expression:įileLocator Pro can search multiple folder paths. Prefix Wildcard expression with NOT: to exclude certain file types from being searched. OR, alternatively as a Wildcard expression it would be: In a previous post I talked about ‘pushing a button that I think does nothing’.You can search multiple files by using regular expressions or Wildcard expressions. Job done? Not quite but it’s one more step in cementing FileLocator Pro’s place as the ultimate super fast, rock solid, search and data analysis tool. Our tests on very low powered machines with just 512MB have shown a huge improvement in stability for very large searches and so far we haven’t received any memory related crash reports. If the search still runs out of memory then rather than crashing, as it did previously, it terminates the search. Results for each file are reduced to around 20 lines, with a maximum of 256 characters per line, and the restriction is retained until the search finishes. If during a search that limit is reached FileLocator Pro starts restricting the search. Based on the amount of memory installed on the machine FileLocator Pro sets an upper limit for un-restricted results per search (from 20MB up to around 200MB). The trouble is that FileLocator Pro doesn’t know at the beginning of the search if it’ll find a few hundred files with hits on a few lines (easy), a couple of files with hits on 10,000 lines (not a problem) or a million files with each one reporting hits on 10,000 lines (problem… probably).įileLocator Pro 6.5 introduces a pre-emptive based solution. Finally to make the whole thing just a little bit trickier, what might be a problem on a scrawny 512MB laptop is not necessarily a problem on sturdy 16GB PC. It can be compounded by searching through file types that may not have EOL (End Of Line) markers, such as EXE or DLLs. searching for the letter ‘a’ – which was the actual search phrase in one of the crash reports we received) it can be a problem. However, when searching over a very large data set with criteria that might not be very selective (e.g. Rarely will a file have 10,000 hits or a line have 20,000 characters. That’s not usually a problem when searching in a limited set of files. algorithms that reserved more memory than was necessary, but some of the problems were more subtle function related issues.īy default FileLocator Pro will record up to 10,000 lines of text per file and each line can be up to around 20,000 characters. We found a few problems that were simply bugs in the code, e.g. It didn’t take long to see that FileLocator Pro had a problem on low spec’d machines performing searches where the data was in the gigabyte range and involved millions of files. We’ve had a slow trickle of crash reports over the last few months and while most were odd, quick to fix, edge-case samples the majority have been related to memory management issues. Since then you may have noticed an increase in memory management related upgrades to FileLocator Pro. Based on CrashRpt (an open source product hosted on Google Code) it’s one of the most useful quality control features we’ve ever added, although we hope it’s a ‘feature’ most of our users will never have cause to see. During August 2012 we quietly added a new crash reporting module to FileLocator Pro.