Speedrunning this one today. Skipped yesterday since it was my birthday. I switched out calls to std::cout and std::cerr with Qt logging functions. Fired off an email to the amazing folks at Jetbrains as Buddies of Budgie is in their open source program. As part of being in that program, Jetbrains generously provides licenses that the organization can use for their software such as CLion and RustRover. These licenses last a year at a time and it only takes an email or two towards the end of the licenses to request for it to be extended. While I'm at it, I always mention how the team is leveraging their products. As a couple examples, Campbell (serebit) has been using CLion for Magpie v1 (Budgie's C++ Wayland compositor leveraging wlroots) and RustRover for Magothy (hardware profiling tool). I have been using CLion for budgie-daemon v2 and Koto's Qt6 port. In my experience, CLion has been damn near flawless for C++ development where many others would struggle (whether that be with highlighting, LSP, linting, the debugger tooling), especially with Koto. If you lead an open source community and think Jetbrains tooling would be useful for you, I'd encourage you to check out their Open Source support page. Not an ad here, I just don't want you to waste time fucking with tooling, spend it on being productive instead. Started working on the Display Configuration Batch system (can I just call it DCB from now on?), almost entirely around the class definitions currently. Trying to get a feel of how it'll look at an abstract definition level before writing the actual code. Nothing to show for it yet. That's it for today. Maybe lost the speedrun. Not sorry.