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 657446 - GObject.gir does not contain "notify" signal
GObject.gir does not contain "notify" signal
Status: RESOLVED INCOMPLETE
Product: gobject-introspection
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-08-26 14:36 UTC by Xavier Claessens
Modified: 2015-02-07 16:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Avoid special handling of GObject (5.29 KB, patch)
2011-08-28 09:48 UTC, Pavel Holejsovsky
committed Details | Review
Diff of GObject-2.0.gir before and after patch (3.71 KB, patch)
2011-08-28 09:50 UTC, Pavel Holejsovsky
none Details | Review

Description Xavier Claessens 2011-08-26 14:36:41 UTC
.git generated for GObject does not contains the "notify" signal.
Comment 1 Pavel Holejsovsky 2011-08-28 09:48:01 UTC
Created attachment 194957 [details] [review]
Avoid special handling of GObject

It turns out that most of the special-casing of GObject.Object inside scanner is not needed any more.  This patch removes most of the special-case handling of GObject and GInitiallyUnowned, and this also results in 'notify' signal being present again inside Object.
Comment 2 Pavel Holejsovsky 2011-08-28 09:50:08 UTC
Created attachment 194958 [details] [review]
Diff of GObject-2.0.gir before and after patch

This is diff between GObject-2.0.gir generated before and after patch, illustrating the impact fo the patch.
Comment 3 Johan (not receiving bugmail) Dahlin 2011-08-28 12:59:52 UTC
Review of attachment 194957 [details] [review]:

This looks good to me. 
* The abstract flags appears to be wrong (gobject.c doesn't set them), so I guess it's good that they were removed
* The removal of the writable flag for g_type_instance is probably okay as well, as it should be private

As long as the tests pass we should commit this. Shouldn't break anything, but pushing it to master will get more testing
Comment 4 Pavel Holejsovsky 2011-08-28 13:06:50 UTC
Review of attachment 194957 [details] [review]:

Committed.  Thanks for the review!
Comment 5 Xavier Claessens 2011-08-29 10:14:50 UTC
Tested in gjs and now it finds "notify" signal on the GISignalInfo of GObject. However, the type of the first arg is GI_TYPE_TAG_INTERFACE so it does 
            info = g_type_info_get_interface (type_info);
            info_type = g_base_info_get_type (info);
but that info_type is OBJECT so it will do a g_value_get_object() which asserts because the GValue has type "GParam".
Comment 6 Emmanuele Bassi (:ebassi) 2013-08-26 10:02:52 UTC
given that using GObject::notify in gjs obviously works, is this bug still valid?
Comment 7 Emmanuele Bassi (:ebassi) 2014-11-10 15:50:48 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 8 André Klapper 2015-02-07 16:53:37 UTC
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]