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 701307 - No longer able to examine and respond to changes in RhythmDB
No longer able to examine and respond to changes in RhythmDB
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: Programmatic interfaces
2.99.x
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-30 19:34 UTC by foss.freedom
Modified: 2013-07-04 22:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description foss.freedom 2013-05-30 19:34:30 UTC
Taken from the rhythmbox developers mailing list

 - https://mail.gnome.org/archives/rhythmbox-devel/2013-May/msg00019.html

The entry-changed signal is passing the changes argument as a GLib.Array.

In older rhythmbox versions it used to pass GObject.ValueArray which you could interrogate in python plugins.

There doesnt appear to be a way to do something similar with GLib.Array.

For my plugin Coverart Browser this is serious since there is no longer a method to respond to rhythmbox database changes

Looking at RB-3.0.gir it appears that entry-changed is mapped to GLib.Array now.

Why the change?  How should plugin devs now analyse change signals?
Comment 1 Jonathan Matthew 2013-07-04 22:27:41 UTC
fixed in commit dd14207