design: relations: add missing markup

This commit is contained in:
Reynaldo H. Verdejo Pinochet 2016-12-28 22:57:59 -08:00
parent 089eeed809
commit 74a0c267bd

View file

@ -26,8 +26,9 @@ locking and refcounting.
- creation/destruction requires two unnested locks and 1 refcount. - creation/destruction requires two unnested locks and 1 refcount.
### usage in GStreamer ### usage in GStreamer
* GstBin -> GstElement
* GstElement -> GstRealPad * `GstBin` -> `GstElement`
* `GstElement` -> `GstRealPad`
### lifecycle ### lifecycle
@ -99,7 +100,7 @@ after `_set_parent()` returns TRUE:
+---------+ +-------+ +---------+ +-------+
``` ```
after parent updates ref_pointer to child. after parent updates `ref_pointer` to child.
``` ```
+---------+ +-------+ +---------+ +-------+
@ -109,7 +110,7 @@ after parent updates ref_pointer to child.
+---------+ +-------+ +---------+ +-------+
``` ```
- only one parent is able to \_sink the same object because the - only one parent is able to `_sink` the same object because the
`_set_parent()` method is atomic. `_set_parent()` method is atomic.
- since only one parent is able to `_set_parent()` the object, only - since only one parent is able to `_set_parent()` the object, only
@ -241,12 +242,14 @@ perform other actions on the child (such as signal emission) it should
### usage ### usage
```
GstRealPad -> GstCaps GstRealPad -> GstCaps
GstBuffer -> GstCaps GstBuffer -> GstCaps
GstEvent -> GstCaps GstEvent -> GstCaps
GstEvent -> GstObject GstEvent -> GstObject
GstMessage -> GstCaps GstMessage -> GstCaps
GstMessage -> GstObject GstMessage -> GstObject
```
### lifecycle ### lifecycle
@ -387,7 +390,7 @@ of the other object.
existance of the objects, If one of the objects is disposed, so is existance of the objects, If one of the objects is disposed, so is
the link. the link.
GstRealPad <-> GstRealPad (srcpad lock taken first) `GstRealPad` <-> `GstRealPad` (srcpad lock taken first)
### lifecycle ### lifecycle