Invalid default export file paths preventing export

Issue #515 closed
Robert Leach created an issue

USE CASE: WHAT DO YOU WANT TO DO?

The user wants to export a PDF.

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

  1. Create a new matrix file that TreeView has never seen before (no trees)
  2. Open it in Treeview
  3. Type command-e to export
  4. Select PDF format (not sure if this step is necessary)
  5. Click export
  6. Do not change anything in the resulting save window (use the default location & file name) and click save

CURRENT BEHAVIOR

I haven't quite isolated the circumstances which lead to the error, however if I change the default save location, I can reliably export a file. I tried creating a new .cdt file that TreeView had never seen before and it exported OK, however I tried creating a new matrix file (large_6kx6k-newtest.txt) and got the following error:

stillerrorsonnewfile.png

I am not able to export any file in the default directory that TreeView has seen before. I always get errors like:

secondtimeerrorsout.png

Even if a new file exports the first time in the default location, the second attempt always fails with an error.

Note that the path in the error can't possibly exist because it names a directory as the same name as the input file. I don't know about other OS's, but OS X doesn't allow the same name to be used for 2 different files, even if one is a folder.

Besides, the path reported in the error doesn't match the selected location in the save dialog:

locationdoesnotmatcherror.png

Using the above default save location results in the invalid file path:

/Users/rleach/PROJECT/TREEVIEW/TestData/large_6kx6k-newtest.txt/large_6kx6k-newtest.txt.PDF

EXPECTED BEHAVIOR

The default file path should match what the user accepts in the save dialog and there should not be an error.

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

none

FILES AFFECTED (where the changes will be implemented) - developers only

unknown

LEVEL OF EFFORT - developers only

minor

COMMENTS

Comments (3)

  1. Log in to comment