mirror of
https://gitlab.freedesktop.org/pipewire/pipewire
synced 2024-10-06 16:09:43 +00:00
doc: swap two @ doxygen tags for the backslash ones
This commit is contained in:
parent
08be841a9e
commit
83ed6e0be3
|
@ -15,7 +15,7 @@ invokes that same method on the remote side. Marshalling and de-marshalling is
|
|||
handled transparently by the \ref page_module_protocol_native.
|
||||
The below graph illustrates this approach:
|
||||
|
||||
@dot
|
||||
\dot
|
||||
digraph API {
|
||||
compound=true;
|
||||
node [shape="box"];
|
||||
|
@ -46,7 +46,7 @@ digraph API {
|
|||
obj_node -> impl_node;
|
||||
|
||||
}
|
||||
@enddot
|
||||
\enddot
|
||||
|
||||
It is common for clients to use both the Core API and the Implementation API
|
||||
and both APIs are provided by the same library.
|
||||
|
|
|
@ -10,7 +10,7 @@ PipeWire socket (default: `$XDG_RUNTIME_DIR/pipewire-0`). This approach
|
|||
provides provides address-space separation between the privileged daemon and
|
||||
non-privileged clients.
|
||||
|
||||
@dot
|
||||
\dot
|
||||
digraph pw {
|
||||
compound=true;
|
||||
node [shape="box"];
|
||||
|
@ -46,7 +46,7 @@ digraph pw {
|
|||
sm -> socket;
|
||||
alsa -> kernel;
|
||||
}
|
||||
@enddot
|
||||
\enddot
|
||||
|
||||
As shown above, the protocol is handled by the \ref
|
||||
page_module_protocol_native. From PipeWire's point-of-view this module is just
|
||||
|
|
Loading…
Reference in a new issue