File Save

[GoogleCodeExporter]

There is a confusion between saving the contents of a current shapefile/data 
base and saving a project file. As is, File > Save prompts the user to save a 
new project file. This is fine, except that the project file refers back to the 
original shape file. If one wants to create a new shape file with new 
variables, etc., the only way to do that is to export the file. That seems 
counterintuitive. There needs to be a cleaner distinction between save and 
export. Why was "save as" removed. That would take care of it: save current 
table and shape file etc. as a new file, but not a new project file. This may 
need some thinking for the different formats, but it is not intuitive for 
legacy users.

Original issue reported on code.google.com by lanse...@gmail.com on 20 Apr 2014 at 2:24

[GoogleCodeExporter]

We took away the "Save As" option because of the many difficult issue that came 
from trying to use "Save As" to do an export to a different format.  However, a 
reasonable solution might be to allow "Save As" only within the current format 
type.  To keep it really simiple, we might only allow it for file-formats such 
as Shapefile, Mapinfo, etc.  

Original comment by mmcc...@gmail.com on 21 Apr 2014 at 6:26

[GoogleCodeExporter]

Good suggestion, only allow save as for "files" and only for same type as 
currently in use. That gives backward compatibility for legacy users and 
doesn't break anything in the complex data base exports.

Original comment by lanse...@gmail.com on 21 Apr 2014 at 6:30

[GoogleCodeExporter]

Original comment by mmcc...@gmail.com on 21 Apr 2014 at 9:49

[GoogleCodeExporter]

Fixed in ci 3186.

Original comment by lixun...@gmail.com on 23 Apr 2014 at 9:22

• Changed state: Fixed

[GoogleCodeExporter]

SaveAs is updated as following attached graph. Let me know if you have any 
comments.

User can specify SaveAs to another datasource with same format. e.g. shapefile 
SaveAs shapefile only.
User can also Create a project file with newly created datasource.
User can only SaveAs project file.

Original comment by lixun...@gmail.com on 23 Apr 2014 at 9:25

Attachments:

• [Screen Shot 2014-04-23 at 2.21.48 PM.png](https://storage.googleapis.com/google-code-attachments/geoda/issue-135/comment-5/Screen Shot 2014-04-23 at 2.21.48 PM.png)

[GoogleCodeExporter]

I like the design, but I just updated the trunk, recompiled and it failed my 
very first test.  Here's what I did:

1) Open columbus_shpfile.gda
2) Delete a column as a test change
3) Choose "Save As" and specify new datasource and project names:
columbus_shpfile_1.gda and columbus_1.shp both within the same directory.
4) Error message appears "Failed to open data source. ...."

Original comment by mmcc...@gmail.com on 23 Apr 2014 at 9:32

• Changed state: Accepted

[GoogleCodeExporter]

fixed in 3188.

Original comment by lixun...@gmail.com on 23 Apr 2014 at 10:08

[GoogleCodeExporter]

Can press "Save" button when one of the checked fields has a blank/invalid 
input.  No failure message appears, rather says "Save success".

Original comment by mmcc...@gmail.com on 23 Apr 2014 at 10:18

[GoogleCodeExporter]

Original comment by mmcc...@gmail.com on 24 Apr 2014 at 10:08

• Changed state: Fixed