class Configure
Defined at line 1273 of file fidling/gen/sdk/fidl/fuchsia.ui.composition/fuchsia.ui.composition/cpp/fidl/fuchsia.ui.composition/cpp/markers.h
Clients should first use the Allocator protocol to register a
BufferCollection. This function will fail with BAD_OPERATION unless all clients of the
BufferCollection have set their constraints.
Afterwards, clients should create and configure the images that will
eventually be rendered to using this method. All the buffers in the
collection from 0 to (buffer_count-1) may be used for screen capture.
Clients are responsible for determining the rotation of the display,
and applying the corrective rotation. For instance, if the display is
mounted 90 degrees clockwise (the "top" is on the right, when looking
at the display), then the client should specify a 270 degree rotation
to account for it.
Similarly, the clients are responsible for specifying a buffer big
enough for the rotated image. If the buffer is too small, a best effort
attempt will be made to render the image.
Finally, clients request the server to render the current screen to the
shared buffers using [`GetNextFrame`].
[`Configure`] can be called again with a new BufferCollectionImportToken
if the client wishes to change any of the configuration settings. In
this case all the buffers from the previous call to [`Configure`] will
be released.
Public Members
static const bool kHasClientToServer
static const bool kHasClientToServerBody
static const bool kHasServerToClient
static const bool kHasServerToClientBody
static const bool kHasNonEmptyUserFacingResponse
static const bool kHasDomainError
static const bool kHasFrameworkError
static const uint64_t kOrdinal