NOTE: This part of the configuration is somewhat advanced. Most users will be able to happily deal with EboBar without ever having to do anything in this sheet.
Configuration: Scan definition
|
|
Click on any item on this configuration dialog to find out what it means and
what you can do with it. NOTE: This part of the configuration is somewhat advanced. Most users will be able to happily deal with EboBar without ever having to do anything in this sheet. |
Displays the scan definition that is currently being edited. Whatever is being displayed and edited on all those widgets below, it all applies to that one scan definition only.
What is a scan definition? Before you click the funky widgets here, you should read some more about them first.
NOTE: This part of the configuration is somewhat advanced. Most users will be able to happily deal with EboBar without ever having to do anything in this sheet.
You may rename the current scan definition here.
Click this button to create a new scan definition. You may then customize this new definition at will.
Eliminates the current scan definition. It is not recommended to delete a definition that is still being used by some directories - what do you think are those directories supposed to do if you delete the very definition they are relying on? EboBar warns you before you delete a definition that is in use. If you choose to ignore EboBar's sensible warning, all directories using that definition will use another one. This is most probably not very desirable. So don't do it.
If checked, EboBar will take any folders it finds and adds them to the pool of items you can access via EboBar.
What for? Well, imagine there's this directory "Peterson" in your "my documents" folder. If you check this option, you'll be able to access that directory itself.
This option does not imply whether or not EboBar scans the contents of this folder - this behavior is not set in the scan definition itself; you'll do that in the list of directories to be scanned.
You may set any number of wildcards here that define which files are to be considered only. Any file which does not meet at least one of the wildcard requirements will be ignored.
A wildcard is a pattern or filter. It's basically a string which the filename must match. An asterisk (*) indicates "any number of characters", a question mark (?) means "any character".
So the wildcard "Image???.jpg" for example will only allow files like "Image003.jpg", "Image471.jpg" and "ImageABC.jpg", but not "Image6.jpg" oder "Image3249.jpg".
"Image*.jpg" allows all of the files mentioned above.
"*.jpg" accepts every file that ends with ".jpg".
This wildcard is only applied to the filename, the path in which the file is located does not matter.
Combining wildcards is possible; you can concatenate them with a semicolon. "Image*;Sound*" allows only files that begin with "Image" or "Sound".
If you're good-willed, you can enter "*" here - this will accept every file.
NOTE that in case of shortcuts, the include/exclude filters apply to the name of the file the shortcut points to, not the name of the shortcut itself.
These are the wildcards that define which files will not be accepted. The exclude filter has precedence over the include filter, i.e. even if a file makes it through your rough include filter, it will be discarded if it matches any of the exclude wildcards.