ruby-****@sourc*****
ruby-****@sourc*****
2004年 3月 3日 (水) 04:24:41 JST
-------------------------
REMOTE_ADDR = 217.117.55.140
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/?Gst%3A%3APipeline
-------------------------
= class Gst::Pipeline
In almost all cases, you'll want to use a Gst::Pipeline when creating a
filter graph. The Gst::Pipeline will manage all the scheduling issues,
including threading, as well as provide simple interfaces to common
functions, like 'Play'.
== Object Hierarchy
* Object
* GLib::Instantiatable
* GLib::Object
* Gst::Object
* Gst::Element
* Gst::Bin
* Gst::Pipeline
== Class Methods
--- Gst::Pipeline.new(name=nil)
Constructs a new Gst::Pipeline object.
If element name is ommited (or nil), then the pipeline will receive a guaranteed
unique name, consisting of the "pipeline" string and a number.
If name is given, it will be given the name supplied.
* name: a name for the pipeline.
* Returns: a newly constructed Gst::Pipeline.
- == Constants
- === GstElementFlags
- --- COMPLEX
- --- DECOUPLED
- --- EVENT_AWARE
- --- INFINITE_LOOP
- --- NEW_LOOPFUNC
- --- SCHEDULER_PRIVATE1
- --- SCHEDULER_PRIVATE2
- --- THREAD_SUGGESTED
- --- USE_THREADSAFE_PROPERTIES
-
- === GstObjectFlags
- --- DESTROYED
- --- FLOATING
- --- OBJECT_FLAG_LAST
-
- === GstBinFlags
- --- FLAG_FIXED_CLOCK
- --- FLAG_LAST
- --- FLAG_MANAGER
- --- FLAG_PREFER_COTHREADS
- --- SELF_SCHEDULABLE
-
- === GstElementState
- --- STATE_NULL
- --- STATE_PAUSED
- --- STATE_PLAYING
- --- STATE_READY
- --- STATE_VOID_PENDING
-
== See Also
((<Gst>)).
- ((<lrz>))