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 665553 - Don't issue a depreciation warning for GtkDialog's NO_SEPARATOR flag, even when unused
Don't issue a depreciation warning for GtkDialog's NO_SEPARATOR flag, even wh...
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: introspection
unspecified
Other All
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2011-12-04 21:12 UTC by Holger Berndt
Modified: 2012-02-04 14:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Don't issue a warning for removed flag even when it's not used (982 bytes, patch)
2011-12-04 21:12 UTC, Holger Berndt 		none Details | Review

Description Holger Berndt 2011-12-04 21:12:39 UTC 
Currently, the Gtk+ override is causing a warning during dialog creation with GTK+-3
about the removed override flag NO_SEPARATOR, even when the user didn't try to set
that flag in the first place.

It would be nice to actually only issue that warning if the flag is in fact used,
but hard-coding the previous enum value doesn't seem like a good idea. Looking at
GTK+-3's source code, it doesn't look like the enum value is marked as "blocked"
in any way, so I'm afraid new additions might take over the old value - that's
why attached patch simply removes the warning.
Comment 1 Holger Berndt 2011-12-04 21:12:41 UTC 
Created attachment 202769 [details] [review]
Don't issue a warning for removed flag even when it's not used
Comment 2 Sebastian Pölsterl 2012-02-04 14:57:54 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.