srdusr
aboutsummaryrefslogtreecommitdiffstats
path: root/crates/wayland/src/native_lock.rs
diff options
context:
space:
mode:
authorsrdusr <[email protected]>2026-08-30 20:41:00 +0200
committersrdusr <[email protected]>2026-08-30 20:41:00 +0200
commitf2f9ed1b3f9c49b323ce591eb72a406058d324a4 (patch)
tree12a53c9c527c0a63a4d93ed197af3f9edf2fca79 /crates/wayland/src/native_lock.rs
parentbac91a6162542025676f57afc3e514b88aa65366 (diff)
downloadsrdwm-f2f9ed1b3f9c49b323ce591eb72a406058d324a4.tar.gz
srdwm-f2f9ed1b3f9c49b323ce591eb72a406058d324a4.zip
Indent doc list continuations
Diffstat (limited to 'crates/wayland/src/native_lock.rs')
-rw-r--r--crates/wayland/src/native_lock.rs20
1 files changed, 10 insertions, 10 deletions
diff --git a/crates/wayland/src/native_lock.rs b/crates/wayland/src/native_lock.rs
index 7ec3e9e..b5ff7c3 100644
--- a/crates/wayland/src/native_lock.rs
+++ b/crates/wayland/src/native_lock.rs
@@ -512,16 +512,16 @@ pub(crate) struct NativeLockFrame<'a> {
/// password box's drop shadow, the box itself, and the on-screen keyboard
/// - header/box/keyboard stacked and centered together via `lock_stack_
/// layout`, the same layout `CompState::native_lock_click` hit-tests
-/// against. Mirrors `lock::lock_render_elements`'s shape/signature so both
-/// backends can call whichever mode applies with the same pattern.
-/// Takes every buffer by reference rather than `&mut CompState`, same
-/// reasoning `lock::lock_render_elements`'s own doc comment gives for
-/// taking a bare surface instead: both backends' render loops call this
-/// while already holding a field-specific `&mut` borrow (`self.udev`/the
-/// winit backend's own renderer), not a whole-`self` one, so a caller has
-/// to extract every field of `NativeLockFrame` *before* that borrow
-/// starts (cheap `MemoryRenderBuffer` clones, not a deep pixel copy) and
-/// pass the clones in.
+/// against. Mirrors `lock::lock_render_elements`'s shape/signature so both
+/// backends can call whichever mode applies with the same pattern.
+/// Takes every buffer by reference rather than `&mut CompState`, same
+/// reasoning `lock::lock_render_elements`'s own doc comment gives for
+/// taking a bare surface instead: both backends' render loops call this
+/// while already holding a field-specific `&mut` borrow (`self.udev`/the
+/// winit backend's own renderer), not a whole-`self` one, so a caller has
+/// to extract every field of `NativeLockFrame` *before* that borrow
+/// starts (cheap `MemoryRenderBuffer` clones, not a deep pixel copy) and
+/// pass the clones in.
pub(crate) fn native_lock_render_elements<R>(frame: NativeLockFrame<'_>, output_size: (i32, i32), renderer: &mut R) -> Vec<MemoryRenderBufferRenderElement<R>>
where
R: Renderer + ImportAll + ImportMem,