pub struct RiverLayoutV3 { /* private fields */ }
Expand description
receive and respond to layout demands
This interface allows clients to receive layout demands from the compositor for a specific output and subsequently propose positions and dimensions of individual views.
See Event
for the list of possible events.
Implementations§
Source§impl RiverLayoutV3
impl RiverLayoutV3
Sourcepub fn destroy<D>(self, conn: &mut Connection<D>)
pub fn destroy<D>(self, conn: &mut Connection<D>)
destroy the river_layout_v3 object
This request indicates that the client will not use the river_layout_v3 object any more.
Since version 1.
Sourcepub fn push_view_dimensions<D>(
self,
conn: &mut Connection<D>,
x: i32,
y: i32,
width: u32,
height: u32,
serial: u32,
)
pub fn push_view_dimensions<D>( self, conn: &mut Connection<D>, x: i32, y: i32, width: u32, height: u32, serial: u32, )
propose dimensions of the next view
This request proposes a size and position for a view in the layout demand with matching serial.
A client must send this request for every view that is part of the layout demand. The number of views in the layout is given by the view_count argument of the layout_demand event. Pushing too many or too few view dimensions is a protocol error.
The x and y coordinates are relative to the usable area of the output, with (0,0) as the top left corner.
Since version 1.
Sourcepub fn commit<D>(
self,
conn: &mut Connection<D>,
layout_name: CString,
serial: u32,
)
pub fn commit<D>( self, conn: &mut Connection<D>, layout_name: CString, serial: u32, )
commit a layout
This request indicates that the client is done pushing dimensions and the compositor may apply the layout. This completes the layout demand with matching serial, any other requests sent with the serial are a protocol error.
The layout_name argument is a user-facing name or short description of the layout that is being committed. The compositor may for example display this on a status bar, though what exactly is done with it is left to the compositor’s discretion.
The compositor is free to use this proposed layout however it chooses, including ignoring it.
Since version 1.
Trait Implementations§
Source§impl Borrow<ObjectId> for RiverLayoutV3
impl Borrow<ObjectId> for RiverLayoutV3
Source§impl Clone for RiverLayoutV3
impl Clone for RiverLayoutV3
Source§fn clone(&self) -> RiverLayoutV3
fn clone(&self) -> RiverLayoutV3
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more