-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
save automatically creates project file #386
Comments
forgot to specify using 1.7.101 |
did you have weights specified? On 1 April 2016 at 07:45, Luc Anselin [email protected] wrote:
Julia Koschinsky, Ph.D. http://geodacenter.asu.edu |
no weights, only operation was to convert a csv file (non-spatial) to a dbf file and edit
|
I agree, I think it makes sense to automatically save the project file when On 1 April 2016 at 07:50, Luc Anselin [email protected] wrote:
Julia Koschinsky, Ph.D. http://geodacenter.asu.edu |
Add restriction to automatically save the project file when time groups are specified
Please verify in 1.7.103 |
1.7.103 Right now when you specify time or weights and save/close, the project file isn't added, so you would lose the time groupings and loaded weights. For those two cases (having time groupings or weights), can we automatically add a project file so these specs aren't lost? |
i have also had some instances where the weights information was not saved into the project
|
Verified in GeoDa 1.7.103 (OSX Yosemite, 10.10.5 Confirmed that .gda file is now saved with either weights or time grouped variables. |
after making some changes to a table (e.g., editing a variable name) and using Save (either the toolbar button or the File > Save command), a project file is automatically created, even when none exists. is that the desired behavior? I would suggest not creating a project file when none currently exists, and only creating it when there already is one. This is "save" of a "current" state, so why create new files.
The text was updated successfully, but these errors were encountered: