[gstreamer-bugs] [Bug 334639] New: API: need API for elements to register custom messages

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=334639
 GStreamer | gstreamer (core) | Ver: HEAD CVS

           Summary: API: need API for elements to register custom messages
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Some elements post custom messages on the bus on certain occasions, and in 0.10
this has become the primary means of communicating things to the application
that don't need to be caught synchroneously, increasingly replacing GObject
signals.

However, application developers have no way to find out whether an element will
send certain custom messages on certain occasions or what they are called, at
least not without checking the source code.

What we need is at least a simple mechanism for elements to register custom
messages they post, preferably with an optional way to also register structure
fields (name, field type, and description) for each of those custom messages.

That way gst-inspect can show this information to app developers.


-- 
Configure bugmail: http://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.