Gregory's Serveromg, my friend drew a birthday nirik :blobcataww:
i recorded a demo video for the focus-follows-mouse section to showcase it lol
|
30 comments
 narrator: there was still one case where it didn't work due to a bug okay, surely this time it definitely works for all correctly written clients Here's one mainly for people who disable animations: window closing now runs in a transaction with the other windows resizing. This means, no background flicker. There's been another logo discussion in the niri Matrix room with some quite interesting concepts emerging. Here's one by Endg4me_ with edits by bluelinden and myself, and inspiration from a concept by ElKowar. What do you think? I'm working on an "event stream" IPC for niri where you get notified about events as they happen. For example, "workspace switched" or "keyboard layout changed". To give it a good test, I actually started implementing native niri support in Waybar. You can give it a try too: https://github.com/YaLTeR/niri/pull/453#issuecomment-2317110904 I finished the initial event stream IPC implementation for niri. My Waybar fork implements a decent amount of the modules niri/workspaces, niri/window, niri/language. Please give that a try, also anyone who makes IPC scripts or bars please give a try to the event stream IPC itself so we can find any design flaws before merging. The PR you will need: https://github.com/YaLTeR/niri/pull/453#issuecomment-2321730996 Waybar fork is linked from there. Set up CI rustdoc publishing for niri-ipc: https://yalter.github.io/niri/niri_ipc/ This has the entirety of the niri IPC documented, including the new event stream events. After the Waybar maintainer speedran merging my niri modules and releasing, I would feel bad delaying any longer, so here's niri 0.1.9 :) Event stream IPC for bars, better window resizing, properly named outputs, on-demand VRR, out-of-the-box fix for NVIDIA flickering, and other improvements! Made interactive move work on touch (and resize too while I was at it), didn't need that many changes actually Added a bit of rubberbanding before the window is "dragged out" of the layout. Should help avoid unintended layout changes. Along with a few more fixes I did, I think interactive move should be good to merge? It's not 100% perfect and jank free, but I'm fairly sure I got all the important things done. Will give it some more testing. Suddenly, @drakulix showcasing the Cosmic session running on, among other compositors, niri! On the big screen at the Ubuntu Summit 😄 somehow this touch moving under stationary pointer works better than i expected (yes trying to do a precise left click with an elbow was difficult) By the way! I'll be giving a talk at RustCon in Moscow on December, 6! :ablobcatwave: Wherein I will briefly describe what a Wayland compositor is, and then show several testing and profiling workflows that I've been using to keep niri stable, robust and performant. (The invitation to submit a talk was completely unexpected, guess niri found its way into the right eyes. 😅) There will be a recording, though in Russian. Interactive window moving, laptop lid and tablet mode switch binds, mouse and touchpad scroll speed setting in today's niri v0.1.10 release! https://github.com/YaLTeR/niri/releases/tag/v0.1.10 Also, niri-ipc is now on crates.io, but keep in mind that it will not be Rust-semver-stable: https://crates.io/crates/niri-ipc Added scaffolding for layer rules, along with a block-out-from rule. Now you can finally block notifications from screencasts! Though, layer-shell surfaces don't have a "geometry" so if they have shadows or transparent padding, all of that becomes solid black, since niri has no way to know where the "actual content" of the layer surface is (that's what geometry is for windows). Thanks to Christian Meissl's fix in Smithay, the git version of niri correctly shows nested pop-up menus in lxqt-panel. They also submitted a fix for invalid pop-up spawning to ironbar, which makes it work on Smithay compositors. Somehow, a small change for tests escalated into trying to completely refactor how animation timing works in niri. And right now I find myself at the exact opposite of this picture. Unfortunately, time has not stopped and is causing problems Like three complete refactors later, I think it's... working? For real this time? No weird issue is gonna sneak up that undermines the whole design? Nothing seems to have caught on fire after one more day of personal testing and one more day in main. So here's a technical page I wrote about the the new niri animation timing design and its motivations: https://github.com/YaLTeR/niri/wiki/Animation-Timing Today I merged a PR by FluxTape which adds "always empty workspace before first" to niri. At the surface this is just a simple config flag with obvious behavior, but it's actually full of edge cases! Things like which workspace to focus at startup. The code refers to workspaces by index in many places, and those all shift when you suddenly insert an empty workspace at index 0. Took several days to catch them all even with our randomized tests, but I think it should be good now. >did a +4,657 −4,237 refactor in the layout code This morning was my niri (-adjacent) talk! :ablobcatbongo: Went really well, got many interesting questions! They promised us video recordings in a few days, so I'll post a link when I get it. Though of course the talk is in Russian.  Turns out, there's a lot of details to get right when implementing a floating window space. For example, dialog windows should always show above their parent window. Otherwise, it's easy to lose them under the (usually much bigger) parent. The WIP floating branch in niri now handles this properly, even for xdg-desktop-portal dialogs (like file chooser) as long as the app correctly parents them via xdg-foreign. Another piece of the floating puzzle: keeping windows on screen. When you change your monitor scale or resolution, you don't want your floating windows to suddenly go unreachable behind the monitor's new borders. Here I'm resizing a nested niri with three windows, simulating resolution changes. No matter what I do, they always remain partially visible and reachable. Even for more unusual cases like trying to resize a window into out of bounds. |
Several days and a lot of hair pulling later, I *think* I got resize transactions working?? Maybe? Hopefully?
Resize transactions is when all windows that must resize together, resize together, with no mismatching frames in between. For example, all windows in a column must add up to the full screen height.
This requires correct configure acks on the client (looking at you, Blender) and very careful state update delaying and resize throttling on the compositor side.
#niri