From 688331024a9fb363f0f7f5e356ffc0c93a23d018 Mon Sep 17 00:00:00 2001 From: ykla Date: Wed, 4 Sep 2024 20:48:06 +0800 Subject: [PATCH] Fix list format --- documentation/asciidoc/computers/camera/rpicam_apps_writing.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/documentation/asciidoc/computers/camera/rpicam_apps_writing.adoc b/documentation/asciidoc/computers/camera/rpicam_apps_writing.adoc index 86287613d..fd5a9217b 100644 --- a/documentation/asciidoc/computers/camera/rpicam_apps_writing.adoc +++ b/documentation/asciidoc/computers/camera/rpicam_apps_writing.adoc @@ -3,6 +3,7 @@ `rpicam-apps` does not provide all of the camera-related features that anyone could ever need. Instead, these applications are small and flexible. Users who require different behaviour can implement it themselves. All of the `rpicam-apps` use an event loop that receives messages when a new set of frames arrives from the camera system. This set of frames is called a `CompletedRequest`. The `CompletedRequest` contains: + * all images derived from that single camera frame: often a low-resolution image and a full-size output * metadata from the camera and post-processing systems