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 652533 - signal definition not being picked up by vapigen
signal definition not being picked up by vapigen
Status: RESOLVED DUPLICATE of bug 731547
Product: vala
Classification: Core
Component: GObject Introspection
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-14 08:39 UTC by Raul Gutierrez Segales
Modified: 2017-03-08 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Raul Gutierrez Segales 2011-06-14 08:39:00 UTC
Given the following GIR definition:

      <virtual-method name="opened">
        <return-value transfer-ownership="none">
          <type name="none" c:type="void"/>
        </return-value>
        <parameters>
          <parameter name="error" transfer-ownership="none">
            <type name="GLib.Error" c:type="GError*"/>
          </parameter>
        </parameters>
      </virtual-method>


....

      <glib:signal name="opened">
        <return-value transfer-ownership="none">
          <type name="none"/>
        </return-value>
        <parameters>
          <parameter name="object" transfer-ownership="none">
            <type name="GObject.Error"/>
          </parameter>
        </parameters>
      </glib:signal>


vapigen will generate this:

                [NoAccessorMethod]
                public virtual bool opened { get; }

and not mark it as a signal.
Comment 1 Rico Tzschichholz 2017-03-08 14:02:32 UTC

*** This bug has been marked as a duplicate of bug 731547 ***