Here, you can edit and test your filters. Filters define which files (or folders) shall be synchronized.
You can test your filter settings, with custom strings (manual mode) or based on current task directories, and files (task based). In manual mode, the filter evaluate every line of text in Query field.
TIPP: if you selected Extension, or Equals simple filters, you can drag and drop files to Definition field. New extensions or filenames added (ver 0.63)
The filter properties implement two type of filters:
- Simple (extension, equal, contain) filter
- Regexp based (case sensitive/insensitive) filter
Simple filters:
Easy to use simple filtering. Evaluation is based on filter definition field value. All simple filters are case insensitive, and you can add multiple values, separated with semicolon (Example: a;b; c;). If definition field value is empty, the filter is disabled (all files/folders accepted).
Extension:
Case insensitive extension-based file filtering. You can define multiple extensions. Special extension separator chars (. and *) accepted, but not required.
Example:
Filter definition: .dAt; *.sav; exe
Matches: example.DaT; Example.sav
Doesn’t match: example.data; example.exe.bak
Equals
Case insensitive string equalisation.
Example:
Filter definition: apple.dat; apple.sav
Matches: Apple.dat; Apple.sav
Doesn’t match: Apple1.dat; Apple.save
Contains
Case insensitive strings contained.
Example:
Filter definition: apple; peach
Matches: Apple.dat; Yellow.Peach.sav
Doesn’t match: Aple1.dat; P3ach.save
Advanced RegExp filters
These filters are based on Java regular expressions. You can find a detailed guide about the “RegExp” explanations used by the filter here. The evaluation uses include and exclude fields.
The include/exclude evaluation sequence is:
validate include regexp
if include regexp definition is empty -> accept file/dir
if include regexp isn’t empty, evaluate include regexp
if not match -> not accept file/dir
if match
validate exclude regexp
if exclude regexp definition is empty -> accept file/dir
if exclude regexp definition isn’t empty, evaluate exclude regexp
if match -> not accept file/dir
if not match -> accept file/dir
Example:
- Include regexp: ^.*\.exe
- Exclude regexp: alma
Input: peach.exe
Result: true
Input alma.exe
Result: false