diff options
| author | srdusr <[email protected]> | 2024-08-03 20:07:00 +0200 |
|---|---|---|
| committer | srdusr <[email protected]> | 2024-08-03 20:07:00 +0200 |
| commit | 35a28a257644483495ac2bd6a5fb1e109e8c1f26 (patch) | |
| tree | 37944a7a2a61bf7ff977fa6349742d1a53ed5ad3 /crates/wayland/src/winit/events.rs | |
| parent | f166df4d979162ae09b439c87cdc64f2b0981308 (diff) | |
| download | srdwm-35a28a257644483495ac2bd6a5fb1e109e8c1f26.tar.gz srdwm-35a28a257644483495ac2bd6a5fb1e109e8c1f26.zip | |
Fix doc-comment file references left stale by today's six module splits
~17 comments across the codebase still pointed at udev.rs/winit.rs/
state.rs by their old flat-file names after those became udev/,
winit/, state/ directories - found while auditing what this work
rushed, since the split verification (function/struct-name diffing,
full test suite) checked structural correctness but never comment
accuracy. Updated each to either the specific new file (e.g. "see
state.rs's REPEAT_DELAY" -> "see state/mod.rs's REPEAT_DELAY",
"udev.rs's monitors()" -> "udev/platform.rs's monitors()") or the bare
module name where the reference was already generic ("the udev/winit
backends", not a specific location).
Diffstat (limited to 'crates/wayland/src/winit/events.rs')
| -rw-r--r-- | crates/wayland/src/winit/events.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/crates/wayland/src/winit/events.rs b/crates/wayland/src/winit/events.rs index 017b7d0..83183f2 100644 --- a/crates/wayland/src/winit/events.rs +++ b/crates/wayland/src/winit/events.rs @@ -18,7 +18,7 @@ pub(super) fn handle_winit_event(state: &mut CompState, output: &Output, event: // This backend had no scroll handling at all - `InputEvent:: // PointerAxis` fell into the catch-all below and was silently // dropped, unconditionally, on every device. Same forwarding as - // `udev.rs`'s equivalent (see its own comment for the `stop()`/ + // `udev/session.rs`'s equivalent (see its own comment for the `stop()`/ // `v120()` reasoning); duplicated rather than shared since the two // backends' `InputEvent` generic parameters differ and there's no // shared event type to write one function against. |