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 623660 - Gtk{Window,Invisible}.has_user_ref_count missing accessor
Gtk{Window,Invisible}.has_user_ref_count missing accessor
Status: RESOLVED NOTABUG
Product: gtk+
Classification: Platform
Component: Widget: Other
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 597610
 
 
Reported: 2010-07-06 08:55 UTC by John Stowers
Modified: 2010-07-13 05:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Stowers 2010-07-06 08:55:47 UTC 
For building PyGtk against Gtk-3.0 [1]

These are both use in PyGtk's custom sink funcs. AFAICT they seem to be a synonym
for checking the object has not been destroyed. 

[1] http://mail.gnome.org/archives/gtk-devel-list/2010-July/msg00005.html
Comment 1 Christian Dywan 2010-07-06 09:34:18 UTC 
Usually you would use 'gtk_object_get_flags () & GTK_IN_DESTRUCTION' to find out if an object is being destroyed. Did you consider that?
Comment 2 John Stowers 2010-07-09 03:47:42 UTC 
AFIACT from http://library.gnome.org/devel/gtk/unstable/GtkObject.html#GTK-OBJECT-FLAGS:CAPS

This is also deprecated. Any idea?
Comment 3 John Stowers 2010-07-13 05:37:03 UTC 
Closing.

This seems to be unnecessary with the new sink functions in pygobject 2.22