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 755498 - timedvaluecontrolsource: Use g_sequence_lookup where possible
timedvaluecontrolsource: Use g_sequence_lookup where possible
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 1.7.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-09-23 21:13 UTC by Jan Alexander Steffens (heftig)
Modified: 2015-10-02 14:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (3.32 KB, patch)
2015-09-23 21:13 UTC, Jan Alexander Steffens (heftig)
committed Details | Review

Description Jan Alexander Steffens (heftig) 2015-09-23 21:13:37 UTC
Created attachment 311982 [details] [review]
patch

When looking for exact matches in the sequence, this results in much simpler code than when using g_sequence_search.

Discovered while trying to solve bug 755496. I also have a workaround for that one, in case the change to g_sequence_search behavior is deliberate.
Comment 1 Sebastian Dröge (slomo) 2015-09-24 07:31:19 UTC
The GLib change was an accident it seems
Comment 2 Sebastian Dröge (slomo) 2015-10-02 14:30:59 UTC
commit d3e9f553024262839c34a6ca178470b36162637c
Author: Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
Date:   Wed Sep 23 23:03:29 2015 +0200

    timedvaluecontrolsource: Use g_sequence_lookup where possible
    
    When looking for exact matches in the sequence, this results
    in much simpler code than when using g_sequence_search.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=755498