After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 69482 - Fix handling of EPSILON in gtkspinbutton.c
Fix handling of EPSILON in gtkspinbutton.c
Status: RESOLVED NOTABUG
Product: gtk+
Classification: Platform
Component: Widget: Other
1.3.x
Other Linux
: Normal normal
: Need diagnosis
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2002-01-23 19:49 UTC by Owen Taylor
Modified: 2007-02-16 11:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Owen Taylor 2002-01-23 19:49:14 UTC 
gtkspinbutton.c tries to do fuzzy comparions by writing:

 a < b

as:

 a - b <= EPSILON

For a "random" EPSILON. But that isn't right since we
are using floating point numbers here, not fixed point
numbers... imagine a = 1e200 b = 1.00000000000001e200.

I'm not really sure what the best way to do this is.
Comment 1 Matthias Clasen 2002-04-05 13:34:04 UTC 
Move open bugs from milestones 2.0.[012] -- > 2.0.3, since 2.0.2 is already out.
Comment 2 Elijah Newren 2004-06-19 18:42:31 UTC 
Mass changing gtk+ bugs with target milestone of 2.4.2 to target 2.4.4, as
Matthias said he was trying to do himself on IRC and was asking for help with. 
If you see this message, it means I was successful at fixing the borken-ness in
bugzilla :)  Sorry for the spam; just query on this message and delete all
emails you get with this message, since there will probably be a lot.
Comment 3 Tim Janik 2007-02-13 15:34:39 UTC 
i have addressed the issues involved with using floating point values calculated by spin buttons or ranges in the GtkAdjustment documentation now:

http://developer.gnome.org/doc/API/2.0/gtk/GtkAdjustment.html#numerical-precision

so i'd like to close this bug RSN unless any further objections come up.