Export path does not entering path relative to the location of the operation_config.xml

zenwalk / mapaction-toolbox

Automatically exported from code.google.com/p/mapaction-toolbox

0 stars 0 forks source link

Export path does not entering path relative to the location of the operation_config.xml #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Create a new operation_config.xml using the OCT
2. Enter a valid value for the export path
3. Access the same crash move folder from a different path (eg over an network 
drive)
4. The export path will no longer be valid.

What is the expected output? What do you see instead?
The export path should be stored as a value relative to the location of the 
operation_config.xml file, making the xml file and the crash move folder more 
portable.

Original issue reported on code.google.com by andrewphilipsmith on 4 Mar 2013 at 9:11

Blocking: #61

GoogleCodeExporter commented 9 years ago

Original comment by andrewphilipsmith on 21 Jul 2013 at 8:08

Added labels: Priority-High, Milestone-Release3.0
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

Original comment by andrewphilipsmith on 22 Jul 2013 at 9:04

GoogleCodeExporter commented 9 years ago

Original comment by andrewphilipsmith on 22 Jul 2013 at 9:06

Added labels: Type-Defect
Removed labels: Type-Enhancement

GoogleCodeExporter commented 9 years ago

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

Now blocking: #61

GoogleCodeExporter commented 9 years ago

Original comment by andrewphilipsmith on 30 Aug 2013 at 1:29

GoogleCodeExporter commented 9 years ago

An initial fix for this has been made. When the export path is written to the 
operation_config.xml file it is first converted to a path relative to the crash 
move folder. As the operation_config.xml file is read in it is converted back 
to an absolute local path. Whilst this works technically (I believe!) I don't 
think it is entirely satisfactory since the user still sees absolute paths in 
both the Config Tool and Export Tool. This implies to the user that the tool 
operates on absolute paths and they would have no reason to suspect that the 
tool is doing the "right thing" behind the scenes.

I have marked this as fixed and ready for QA for version 3.0. I've opened a 
separate ticket (issue 67 
http://code.google.com/p/mapaction-toolbox/issues/detail?id=67) to track the 
GUI concerns for a later release.

Original comment by andrewphilipsmith on 30 Aug 2013 at 10:44

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Fixed with relative path stored in the config xml

Original comment by hcpick...@googlemail.com on 14 Jun 2014 at 3:02

Changed state: Verified