template <>class WireSyncClientImpl
Defined at line 821 of file fidling/gen/sdk/fidl/fuchsia.ui.composition.internal/fuchsia.ui.composition.internal/cpp/fidl/fuchsia.ui.composition.internal/cpp/wire_messaging.h
Methods to make a sync FIDL call directly on an unowned handle or a
const reference to a |::fidl::ClientEnd
<
::fuchsia_ui_composition_internal::ScreenCapture>|,
avoiding setting up a client.
Public Methods
::fidl::WireResult< ::fuchsia_ui_composition_internal::ScreenCapture::Configure> Configure (::fuchsia_ui_composition_internal::wire::ScreenCaptureConfig ScreenCaptureConfig)Clients should first use the ['fuchsia.ui.composition/Allocator']
protocol to register a BufferCollection.
Similarly, the clients are responsible for specifying a buffer big
enough for the image. If the buffer is too small, an
attempt will be made to render the image, however, it will not be
guaranteed to contain the complete image.
Allocates 96 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_ui_composition_internal::ScreenCapture::GetNextFrame> GetNextFrame ()[`GetNextFrame`] returns the latest unseen-by-the-client frame as soon
as possible. On the first call to [`GetNextFrame`] and any subsequent
calls that have not recieved the previous expected requested frame,
[`GetNextFrame`] will return immediately with the last frame to be
rendered. If the client had requested the previous frame, the server
will wait until the next frame is produced to return.
After the client finishes processing the returned buffer, they should
drop the eventpair to signal to the server that the buffer can be
re-used.
It is invalid to call [`GetNextFrame`] while a previous call is still
pending. Doing so will return a BAD_HANGING_GET error and cause the
channel to close.
Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.