From 3cae9335799e0e73bf356368696ca68fb59be0d6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tim-Philipp=20M=C3=BCller?= Date: Sun, 28 Aug 2016 16:02:14 +0100 Subject: [PATCH] tools: gst-inspect: don't print internal pad request function name This just confuses people, they look at it and try to call it directly by name, instead of using the public GstElement API. It stands to reason that it goes without saying that when an element provides request pads that they can actually be requested using the standard API, and there's no point in printing internal implementation details of the element. --- tools/gst-inspect.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/tools/gst-inspect.c b/tools/gst-inspect.c index 5c93b4f769..4d020ad8ab 100644 --- a/tools/gst-inspect.c +++ b/tools/gst-inspect.c @@ -541,7 +541,6 @@ print_element_properties_info (GstElement * element) static void print_pad_templates_info (GstElement * element, GstElementFactory * factory) { - GstElementClass *gstelement_class; const GList *pads; GstStaticPadTemplate *padtemplate; @@ -551,8 +550,6 @@ print_pad_templates_info (GstElement * element, GstElementFactory * factory) return; } - gstelement_class = GST_ELEMENT_CLASS (G_OBJECT_GET_CLASS (element)); - pads = gst_element_factory_get_static_pad_templates (factory); while (pads) { padtemplate = (GstStaticPadTemplate *) (pads->data); @@ -571,8 +568,6 @@ print_pad_templates_info (GstElement * element, GstElementFactory * factory) n_print (" Availability: Sometimes\n"); else if (padtemplate->presence == GST_PAD_REQUEST) { n_print (" Availability: On request\n"); - n_print (" Has request_new_pad() function: %s\n", - GST_DEBUG_FUNCPTR_NAME (gstelement_class->request_new_pad)); } else n_print (" Availability: UNKNOWN!!!\n");