message DragImage
Control plane
message DragImage
What hangs off the cursor during a drag out of a Lava window, as the
client drew it. See StartDrag.
A draw list rather than a picture, for the reason every frame is one: the
client has no GPU to rasterise with, and a chip's commands are a few
kilobytes where its pixels would be hundreds. The client lays its views
out at their natural size and emits them with the chip's top-left at 0,0;
width × height is what that came to.
The arrays are canvas's DrawCommand (32 bytes), GlyphInstance (16),
MeshVertex (8) and GradientDesc (16), raw — both ends compile against
draw_command.hpp, and the compositor refuses any array that is not a
whole number of them. Font and image ids in them are the device-wide ids
the client already registered, so a chip can carry text and pictures.
idl/lava.npidl:878
Fields
commands: vector<u8>
Not documented.
idl/lava.npidl:883
glyphs: vector<u8>
Not documented.
idl/lava.npidl:884
gradients: vector<u8>
Not documented.
idl/lava.npidl:886
height: u32
Not documented.
idl/lava.npidl:880
meshVertices: vector<u8>
Not documented.
idl/lava.npidl:885
offsetX: f32
Not documented.
idl/lava.npidl:881
offsetY: f32
Not documented.
idl/lava.npidl:882
width: u32
Not documented.
idl/lava.npidl:879