a deep read of both dispatches for budgie lovers:
"for some reason the generated client headers and public code from ecm_add_wayland_client_protocol weren't being discovered properly during the build phase. I still haven't figured out what the hell is doing on with that and figured "screw it", I'll continue some refactoring and have my classes inherit from generated QtWayland::CLASS interfaces from QtWaylandScanner. I wasn't originally going to, at least after feeling so defeated yesterday, but after some tinkering toSo not quite the route I was expecting to already be doing down before even making the damn thing a public repo, but I know I will be much prouder of the work once it is all said and done!day I very quickly realized how much cleaner the code will be by leveraging the generated interfaces...
..Plan for tomorrow is to go through the rest of my code where I was using WaylandOutputManager and swap them over to the orchestrator, then hook up some signals / slots that I set up today as I was working on the classes. After all, that's the reason I shifted it to being a Qt application instead of a generic C++ one at all -- the Qt event loop and signals / slots make callbacks much easier! Will be interesting to see if this thing flies when all is said and done 🙂"
**Wayland to Budgie the old fashioned way: pure grit and determination by a strobl with his sleeves rolled up. gotta love it.
