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 696930 - Incorrect allowed value for a property
Incorrect allowed value for a property
Status: RESOLVED FIXED
Product: gtk-doc
Classification: Platform
Component: general
1.18
Other Linux
: Normal normal
: 1.19
Assigned To: gtk-doc maintainers
gtk-doc maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-30 22:37 UTC by Gabríel Arthúr Pétursson
Modified: 2013-05-30 17:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Gabríel Arthúr Pétursson 2013-03-30 22:37:07 UTC 
Under certain circumstances, the allowed value shown for properties in incorrect.

https://developer.gnome.org/gtk3/3.8/GtkBox.html#GtkBox--c-position

Take the "position" property for GtkBox as an example. "Allowed values: >= G_MAXULONG"

That is not correct for a number of reasons. First, the type of that property is gint. Second, why say greater-that-or-equal-to, instead of just equal-to? Third, the default of 0 value wouldn't be allowed.

The corresponding source code:
https://git.gnome.org/browse/gtk+/tree/gtk/gtkbox.c?h=gtk-3-8#n310
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2013-05-30 17:56:27 UTC 
commit a9aa6ca34a97a2e10e3747e8057bcd8bdb6d3ad3
Author: Stefan Sauer <ensonic@users.sf.net>
Date:   Thu May 30 19:54:33 2013 +0200

    scangobj: fix description for int properties
    
    Don't try to apply unsigned MAX constants to signed properties.
    Fixes: #696930