Top | ![]() |
![]() |
![]() |
![]() |
GstValidateReporterGstValidateReporter — A GInterface that allows GObject to be used as originator of issues in the GstValidate reporting system |
#define | GST_VALIDATE_REPORT() |
void | gst_validate_reporter_set_handle_g_logs () |
void | gst_validate_report () |
gint | gst_validate_reporter_get_reports_count () |
#define GST_VALIDATE_REPORT(m, issue_id, ...)
Reports a new issue in the GstValidate reporting system with m
as the source of that issue.
m |
The GstValidateReporter where the issue happened |
|
issue_id |
The GstValidateIssueId of the issue |
|
... |
The format of the message describing the issue in a printf format, followed by the parameters. |
void
gst_validate_reporter_set_handle_g_logs
(GstValidateReporter *reporter
);
Set reporter
has the 'source' of any g_log happening during the
execution. Usually the monitor of the first GstPipeline is used
to handle g_logs.
Basically this function is used in order to start tracking any issue reported with g_log in the process into GstValidate report in the GstValidate reporting system.
void gst_validate_report (GstValidateReporter *reporter
,GstValidateIssueId issue_id
,const gchar *format
,...
);
Reports a new issue in the GstValidate reporting system with m
as the source of that issue.
You can also use GST_VALIDATE_REPORT instead.
gint
gst_validate_reporter_get_reports_count
(GstValidateReporter *reporter
);
Get the number of reports present in the reporter.
“validate-runner”
property“validate-runner” GstValidateRunner *
The Validate runner to report errors to.
Flags: Read / Write / Construct Only