Fix for version 201 #1820
Merged
Fix for version 201 #1820
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is caused by new feature: saving encoded characters in geoda.
Make the full extent set using the top layer bounding box; When reorder layers in MapLayerSettings dialog, set map extent using top layer bounding box automatically;
prevent reset extent when change layer order after zoom/pan
fix: editing is limited to 10 digits in a integer field in table update the logic of resize column width based on content instead of using column lable width;
when GeoDa loads a table-only data source, only "Variables" based "Distance Weight" is enabled in Weights File Creation dialog.
Set to use default en_US number formatting, which use DOT as decimal separator internal. If COMMA decimal separator used in data (e.g. csv), GeoDa will read the value as string by default, and user can convert the field from string to real by automatically detecting if DOT/COMMA used as decimal separator.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#1818 Edit String content in Table crashes GeoDa in V197
#1817 bounding box issue with multiple layers
#1810 Table - stack: problem with edit variable properties
#1809 Enhancement for Chinese translation
#1819 Table: editing is limited to 10 digits in an integer field
#1815 UI update for weights creation dialog when loading a table-only dataset
fix: converting column (string type) with numbers using comma as a decimal separator to real type.
enhancement: support case sensitive “variable names” on some data format e.g. ESRI shapefile)