Problem is not in internal floating point operations but in UI inconsistency of mouse and keyboard operations. I can get -0.00 using mouse (and this -0.0 will be restored after file reopening) but I can't enter it via keyboard — unnecessary minus is just discarded. I believe that mouse operations should follow same logic and just discard it.
Timur. On Sun, 2018-12-23 at 11:27 +0100, Matthieu Moy wrote: > ----- Original Message ----- > > From: "Timur Irikovich Davletshin" <timur.davlets...@gmail.com> > > I'm not sure if this is a bug or something I don't understand. > > > > Bauhaus controls let me specify (and eventually store) negative > > zeros > > like -0.00EV in exposure module. Is it different from 0.00EV or > > there > > is some hidden rounding problem like -0.0000001? > > Probably just a consequence of using floating point numbers in the > implementation. > > Floating points accept +0.0 and -0.0, but these numbers behave the > same in almost all operations (+0.0 == -0.0 for example). AFAIK the > only different thing is that 1/+0.0 == +infinity while 1/-0.0 == > -infinity. You may care about that as a programmer writing very > tricky programs with floating point numbers, but as a darktable user, > they are just the same! > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
