Lines Matching refs:will

12 Events will be generated by either a plugin or the app. It should be
39     handler will be implemented for pads that don't implement their own 
77 places. This will be done by calling gst_pad_event() on a pad.
79 A first implementation will only cover inserting events on src pads
87 will for example change the state of an element to the PAUSED state. Not
88 sure when or how this will happen.
96 filesrc will read until it reaches EOF. It will then create a GstEvent
97 of type EOS and return it in the _get function. The event will travel
98 downstream and will reach the fakesink element. Fakesink will detect
99 the event in the _chain function and will call the default handler. The
100 default handler will set the element to the paused state. filesrc will
107 on filesrcs src pad with the SEEK event type. The event handler will
108 react and change filesrcs internal status. filesrc will return a DISCONT
118 the event will travel upstream using the handlers and the intermediate
122 Filesrc will get a byte seek event on its src pad and will proceed as
125 As can be seen from this example the app will generate an event in another
126 context than those of the plugins, so this will need proper locking.