Closed GoogleCodeExporter closed 9 years ago
correct that, it is not zero, but a huge number of decimals, see attached.
Original comment by lanse...@gmail.com
on 23 Apr 2014 at 2:11
Attachments:
Further investigation reveals that the number of displayed decimals is being
initialized to "-1" for the new fields. -1 is supposed to indicate "use
default" but is being incorrectly left as the actual value in this case. For
dBase, displayed decimals value is stored as an unsigned char, which would
explain why -1 becomes 255 after the dBase file is saved and then reloaded.
There is no problem with the dBase save per say, but rather something is wrong
with the merge or perhaps internal DbfTable initialization. This will be fixed
shortly.
Original comment by mmcc...@gmail.com
on 23 Apr 2014 at 7:40
Resolved by revision 3185. Will appear in GeoDa 1.5.33
Original comment by mmcc...@gmail.com
on 23 Apr 2014 at 8:05
Original issue reported on code.google.com by
lanse...@gmail.com
on 23 Apr 2014 at 1:58Attachments: