Thank you for reporting this issue. I had naively assumed that Float.MIN_VALUE would represent the minimum value of a Float as opposed to your suggested -Float.MAX_VALUE. Why the choice was made to use this constant name for the precision of a Float and not having Float.MIN_VALUE be defined to be - Float.MAX_VALUE, I do not know, but I will fix this in the HDFView source.
From: Hdf-forum <email@example.com> on behalf of Jonathan JaraAlmonte <firstname.lastname@example.org>
Sent: Wednesday, November 22, 2017 9:31:54 AM
Subject: [Hdf-forum] Bug in hdfview table editor
I am using hdfview 3.0 and found an issue with the table editor. For float datasets, you cannot enter and validate a negative number. The issue is in hdf.view.Tools.checkValidFloat where Float.MIN_VALUE is erroneously used instead of -Float.MAX_VALUE as the lower bound for floats. Thanks,