Config tool does not validate the Export path value

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open Config Tool and create a new op config tool
2. Enter arbitrary string in the export path field under the Setting tab.

What is the expected output?
The tool warn if the value is:
- blank
- includes invalid characters
- does not point to a real, existing directory
- does point to an existng file
- is not expressed as a relative path wrt the crash_move_dir

What do you see instead?
- Any value (including blanks and invalid path names) are accepted without 
warning.

Original issue reported on code.google.com by andrewphilipsmith on 22 Jul 2013 at 11:55

• Blocking: #61

[GoogleCodeExporter]

Original comment by andrewphilipsmith on 17 Aug 2013 at 10:54

• Now blocking: #61

[GoogleCodeExporter]

Original comment by andrewphilipsmith on 30 Aug 2013 at 3:48

• Changed state: Fixed

[GoogleCodeExporter]

tool throws up a warning symbol if the path is not valid as stated

Original comment by gd...@mapaction.org on 16 Aug 2014 at 2:46

• Changed state: Verified