Sam Lantinga
Sam Lantinga
> Only that I didn't expect these large dll sizes only because of aom encoder inclusion (8.9M x86 dll and 13.4M x64 dll) I'm not surprised, the size of the...
> P.S.: We are currently vendoring aom 3.6.1, however 3.7.1+ has at least one CVE fix. I suggest upgrading to aom 3.7.2 or 3.8.1 I used 3.6.1 because that is...
Sure, go for it. However I'm going to ask @madebr's help with these: ``` -- libavif: libyuv not found; libyuv-based fast paths disabled. -- libavif: libsharpyuv not found ```
I think we can vendor it. We already have libsharpyuv in webp.
@Sackzement, can you print out the value of rect and usable in each of those case, before the intersection? I'm guessing the usable rect is relative to the monitor rect,...
@Kontrabant, do we expect Wayland to provide usable bounds here?
So that all makes sense. What's happening is that the usable bounds aren't per-monitor, they're a rectangle across all three monitors that is guaranteed not to intersect the panel. Unfortunately,...
Here's someone asking about this on Stack Overflow: https://stackoverflow.com/questions/2598580/gtk-get-usable-area-of-each-monitor-excluding-panels
X-Tile solves this by taking the monitor bounds and subtracting the areas covered by strut windows: https://github.com/giuspen/x-tile/blob/9ec59c93f3991ab16975fee3215a6236833aa9a2/modules/support.py#L291-L315
I'm not sure if this approach is a good one for our purposes or not. @Sackzement, do you want to prototype it up and see how it works on your...