PadFlags#
- class PadFlags#
Pad state flags
Fields#
- class PadFlags
- ACCEPT_INTERSECT#
The default accept-caps handler will check it the caps intersect the query-caps result instead of checking for a subset. This is interesting for parsers that can accept incompletely specified caps.
- ACCEPT_TEMPLATE#
The default accept-caps handler will use the template pad caps instead of query caps to compare with the accept caps. Use this in combination with
ACCEPT_INTERSECT. (Since: 1.6)
- BLOCKED#
Is dataflow on a pad blocked
- BLOCKING#
Is pad currently blocking on a buffer or event
- EOS#
Is pad in EOS state
- FIXED_CAPS#
The pad is using fixed caps. This means that once the caps are set on the pad, the default caps query function will only return those caps.
- FLUSHING#
Is pad flushing
- LAST#
Offset to define more flags
- NEED_PARENT#
Ensure that there is a parent object before calling into the pad callbacks.
- NEED_RECONFIGURE#
The pad should be reconfigured/renegotiated. The flag has to be unset manually after reconfiguration happened.
- PENDING_EVENTS#
The pad has pending events
- PROXY_ALLOCATION#
The default query handler will forward allocation queries to the internally linked pads instead of discarding them.
- PROXY_CAPS#
The default event and query handler will forward all events and queries to the internally linked pads instead of discarding them.
- PROXY_SCHEDULING#
The default query handler will forward scheduling queries to the internally linked pads instead of discarding them.