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 327238 - gst_parse_launch should have API to provide details on error like missing elements
gst_parse_launch should have API to provide details on error like missing ele...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal enhancement
: 0.10.20
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-16 17:25 UTC by Thomas Vander Stichele
Modified: 2009-01-20 08:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thomas Vander Stichele 2006-01-16 17:25:58 UTC 
This way, it would be possible to actually let you know more useful stuff programatically, like:
- you're missing an element
- name of elementfactories that fail to link
- ...

which would be useful from:
- GNOME apps - telling you what plugin you need to install
- Flumotion
- ...
Comment 1 Wim Taymans 2006-03-23 10:20:32 UTC 
care to make a proposed patch?
Comment 2 André Klapper 2006-10-02 08:25:18 UTC 
thomas: *ping*?
Comment 3 Thomas Vander Stichele 2007-03-11 19:38:39 UTC 
I tried, but the parser code hurts my brain.  Does anyone understand it ?
Comment 4 Tim-Philipp Müller 2008-06-24 20:30:09 UTC 
This is possible now with the new gst_parse_launch_full() + GstParseContext API. The get-names-of-missing-elements-thing has been implemented.

I'm not sure how useful it is to know the name of factories that fail to link - did you have a use case in mind?

If not, can we close this now?
Comment 5 Christoph Wurm 2009-01-19 20:01:34 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!