Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GeoDa memorizes last input in DB input not working; Invalid connection causes crash; #422

Closed
lixun910 opened this issue May 5, 2016 · 3 comments
Closed

GeoDa memorizes last input in DB input not working; Invalid connection causes crash; #422

lixun910 opened this issue May 5, 2016 · 3 comments
Assignees
@lixun910
Labels
bug fixed: verify!
Milestone
1.8

Comments

@lixun910
Copy link
Member

lixun910 commented May 5, 2016

No description provided.

@lixun910 lixun910 self-assigned this May 5, 2016
@lixun910 lixun910 added the bug label May 5, 2016
@lixun910 lixun910 added this to the 1.8 milestone May 5, 2016
lixun910 referenced this issue in lixun910/geoda May 5, 2016
@lixun910
#422 GeoDa Memorize issue; Invalid Connection crash
78c3877
This was referenced May 6, 2016
Merged
Merged
@jkoschinsky
Copy link
Collaborator

jkoschinsky commented May 19, 2016 •
edited
Loading

Xun, could you add a description for this, e.g. is the problem that in this database dialog previously entered DB details were not memorized correctly, and with incorrect entries, the program would crash?

screen shot 2016-05-18 at 7 23 37 pm

@lixun910
Copy link
Member Author

On windows, the previous versions can't memorize the last input of this "database" tab (randomly input)
If you input randomly, it will crash in previous versions.

@jkoschinsky
Copy link
Collaborator

Verified in GeoDa 1.8.7.3 (OSX Yosemite, 10.10.5).

Fixed: Entered random characters: Now program no longer crashes and generates warning instead:

screen shot 2016-05-20 at 9 02 59 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lixun910 lixun910

Labels
bug fixed: verify!
Projects
None yet
Milestone
1.8
Development

No branches or pull requests
2 participants
@lixun910 @jkoschinsky