Fix #595 by correctly handling UINT64_MAX and INT_MAX boundaries
authorSoeren Apel <soeren@apelpie.net>
Mon, 24 Aug 2015 16:21:15 +0000 (18:21 +0200)
committerUwe Hermann <uwe@hermann-uwe.de>
Tue, 25 Aug 2015 16:11:16 +0000 (18:11 +0200)
By using an int64_t to hold UINT64_MAX, it was made to overflow
to -1. This lead to range_min=0 and range_max=-1, resulting in
a disabled spin button.


No differences found