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 334639 - API: need API for elements to register custom messages
API: need API for elements to register custom messages
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal enhancement
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-15 11:23 UTC by Tim-Philipp Müller
Modified: 2006-10-10 14:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim-Philipp Müller 2006-03-15 11:23:57 UTC
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.
Comment 1 Wim Taymans 2006-10-10 14:21:50 UTC
Can we just say that the message needs to be explained in the element documentation as is stated in the docs for @GST_MESSAGE_ELEMENT?
Comment 2 Tim-Philipp Müller 2006-10-10 14:25:17 UTC
Agreed, probably makes more sense (and leads to better docs too).