View Issue Details

IDProjectCategoryView StatusLast Update
0001761Slicer4Core: MRMLpublic2012-08-21 10:01
Reporterpieper Assigned Tonicole  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version 
Target VersionSlicer 4.2.0Fixed in VersionSlicer 4.2.0 
Summary0001761: save scene to directory deletes one level too much
Description

The File->Slicer Data Bundle->Save Scene to Directory option gives a dialog box to select a directory. However it goes up one level higher and deletes the whole directory.

Additional Information

The menu option is disabled in r19457 to avoid accidents.

TagsNo tags attached.

Activities

nicole

nicole

2012-02-28 06:40

administrator   ~0003735

This is expected behaviour (deleting the chosen directory and creating it fresh), as it needs an empty directory to write the files into so that when it bundles it up, nothing extraneous is in there. I can add more warnings/tests/confirmation dialog boxes, though.

nicole

nicole

2012-02-29 09:28

administrator   ~0003743

Okay, verified that this is actually happening, and it's because the wrong directory is being passed to vtkMRMLApplicationLogic::SaveSceneToSlicerDataBundleDirectory
it's getting passed the directory one level up from the one that's chosen.

pieper

pieper

2012-02-29 09:29

administrator   ~0003744

Nicole's right - this should be in the Slicer4 bug tracker!

nicole

nicole

2012-02-29 09:55

administrator   ~0003745

The problem seems to stem from the QFileDialog directory() call - it will return the currently displayed directory, so if you create a new directory and just click on it so that it appears in the Directory text box, directory() will still return the current directory one level up from the one that you created.
Will try to refactor the code to listen for the signal fileSelected instead.

nicole

nicole

2012-02-29 11:26

administrator   ~0003747

svn 19471 uses getExistingDirectory() and confirms that the user wishes to proceed if there are files there.

jcfr

jcfr

2012-07-27 15:36

administrator   ~0005343

Dear issue reporter,

Good news :) Slicer developers SOLVED the problem you reported - YOU now need to VERIFY and CLOSE this issue.

Issue History

Date Modified Username Field Change
2012-02-28 03:26 pieper New Issue
2012-02-28 03:26 pieper Status new => assigned
2012-02-28 03:26 pieper Assigned To => nicole
2012-02-28 06:40 nicole Note Added: 0003735
2012-02-29 09:28 nicole Note Added: 0003743
2012-02-29 09:28 nicole Project Slicer3 => Slicer4
2012-02-29 09:29 pieper Note Added: 0003744
2012-02-29 09:55 nicole Note Added: 0003745
2012-02-29 11:26 nicole Note Added: 0003747
2012-02-29 11:27 nicole Status assigned => resolved
2012-02-29 11:27 nicole Resolution open => fixed
2012-07-27 15:36 jcfr Note Added: 0005343
2012-07-28 09:58 pieper Status resolved => closed
2012-08-21 10:01 jcfr Fixed in Version => Slicer 4.2.0 - Feature freeze Sept 1st 2012
2012-08-21 10:01 jcfr Target Version => Slicer 4.2.0 - Feature freeze Sept 1st 2012