Matthew Brooks

>This is important because it can be architecturally undesirable to remove click handlers and then add them back after the drawing is finished. We used a flag to simply ignore...

I learned about the `include-dirs` directive in Cabal, so I don't need my stupid shell script anymore, and it works in the repl. ```cabal library include-dirs: protocol-headers ``` Tells it...

@bradrn the wlroots header files include other header files, some of which do not seem to be present (at least on my system). Maybe it's because I'm using Nix? The...

@bradrn Welcome back. > if the XML gives enough information to do that — why are we bothering to write all this stuff out manually at all? I thought we...

@bradrn Another reason why I decided that I should check in the non-standard headers was because they are only a transitive dependency of ours. I don't think we need to...

@bradrn I still don't fully understand what's going on, but even other compositors seem to have some sort of build step for running wayland scanner: [hyperwm](https://github.com/hyprwm/wlroots-hyprland/blob/a336b9b1fb415433e849de002df68c45034d0419/protocol/meson.build)

@bradrn Does that mean that I'm on the right track? I honestly wasn't sure. I was kind of going to just going to generate them manually and check them in,...

@bradrn These are headers that describe the Wlroots code (which we're trying to bind to) [wlroots repo files](https://gitlab.freedesktop.org/wlroots/wlroots/-/tree/master/include/wlr/types?ref_type=heads) Among these is wlr_xdg_shell, which has a struct like this: ```c struct...

Something I've been thinking of too is that we might not need to write all of these type definitions. I was wondering if some of the hard ones, ones where...