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.
This commit is contained in:
Tim-Philipp Müller 2016-08-28 16:02:14 +01:00
parent 4714ef2f8e
commit 3cae933579

View file

@ -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");