08:39 <novakane[m]> is there a way to make an if loop if it's a debug build or with some flag maybe?

08:40 <novakane[m]> like if (debug) renderer.clear()

08:41 <ifreund> if (std.builtin.mode == .Debug)

08:45 <novakane[m]> thanks

08:48 <novakane[m]> ifreund: if I make something like if (build_options.damage) I can build it with -Ddamage after?

08:49 <novakane[m]> and adding it to build.zig of course

08:49 <ifreund> indeed, though if this is for a damage debugging feature I'd prefer this to be done a different way

08:50 <ifreund> namely, an undocumented command line option that is only available in debug builds

08:50 <novakane[m]> I want to highlight with color what's rendering or not

08:51 <ifreund> yeah that's exactly what I'm talking about

08:52 <novakane[m]> yeah cause right now I comment/uncomment to try, not ideal

08:52 <novakane[m]> I look into a command then

08:55 <novakane[m]> 'damage-highlight' sounds good to you?

08:55 <ifreund> `river --highlight-damage`?

08:56 <ifreund> a command line option is what I'm picturing, not something you run through riverctl

08:56 <ifreund> though maybe we should just make this a build option...

08:57 <novakane[m]> well is a command line option is hard to add?

08:58 <ifreund> no, not at all

08:59 <novakane[m]> is that in main.zig?

08:59 <ifreund> it's just the question of whether we care about being able to run with damage highlighting without rebuilding or not

08:59 <ifreund> yep river/main.zig

08:59 <ifreund> if we don't care, then a build option would be better

08:59 <novakane[m]> as you want? personnaly I don't care to rebuild

09:01 <novakane[m]> sway use a build option I think

09:01 <ifreund> nah they have hidden command line options

09:01 <emersion> nah, runtime option

09:01 <emersion> -Ddamage=highlight

09:01 <emersion> we were also too lazy to implement a mode to highlight the damaged regions, and fade-out the highlight

09:02 <novakane[m]> oh ok

09:02 <emersion> the current debug code is a one-line glCLear()

09:03 <ifreund> I think if there's just one on/off debug option the build option is preferable, but if we have multiple different debug options then that could get annoying/unwieldy

09:04 <leon-p> if they default to off it would be fine even with multiple. I can't imagine ever wanting to run with multiple debug options

09:05 <ifreund> let's just do build options for now, we can trivially change this later

09:05 <ifreund> focus on what's actually important

09:06 <novakane[m]> sure no problem

12:38 <jaafarrc> I found out why River freezes.

12:38 <jaafarrc> I need to compile River with Xwayland support.

12:38 <jaafarrc> Okay, I didn't find out *why,* but I found out how to mitigate it.

12:38 <jaafarrc> We already know it's because of the damage tracking.

12:39 <jaafarrc> So, yeah, I *think* that fixed it; the last time I compiled River with Xwayland was before I complained about the freezes.