[Bug 720023] [pitivi] GStreamer effect properties are received in random order
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Sun Dec 8 17:02:32 PST 2013
https://bugzilla.gnome.org/show_bug.cgi?id=720023
GStreamer | gst-editing-services | git
Jean-François Fortin Tam <nekohayo> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|HELPWANTED |
Component|introspection |gst-editing-services
Version|3.10.x |git
AssignedTo|nobody at pygtk.org |gstreamer-bugs at lists.freede
| |sktop.org
Product|pygobject |GStreamer
Target Milestone|--- |HEAD
Summary|[pitivi] GStreamer |[pitivi] GStreamer effect
|properties are received in |properties are received in
|random order with GObject |random order
|introspection through |
|PyGObject |
QAContact|python-bindings-maint at gnome |gstreamer-bugs at lists.freede
|.bugs |sktop.org
--- Comment #8 from Jean-François Fortin Tam <nekohayo at gmail.com> 2013-12-09 01:02:24 UTC ---
Ok, that absolves pygobject/g-i from suspicion;
the blame is now to be pointed at GES :)
While we're at it, would be good to check if there are other places in GES'
code where we potentially mangle the order of properties like that. As far as I
can tell (from looking at Pitivi's behavior), this doesn't seem to affect the
properties of the encoders (whew).
---------
<nekohayo> you could probably make [a proof-of-concept script] to demonstrate
the randomness vs non-randomness of GESeffect vs creating the element
directly... [but] since you've spotted the ghashtable, does this even need
proof anyway?
<stormer> I can confirm that GObject.list_properties() return the same order
seen in gst-inspect, which is definition order
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list