Max Verevkin
Max Verevkin
Yes, I pushed my attempt to implement fractional scaling to https://github.com/MaxVerevkin/i3bar-river/tree/wpfs (it works in river btw (I mean the viewport part, river does not implement wp-fs)). Min config: ``` $...
> hyprpaper uses wp-fs-v1 and it's working fine as far as I can tell. Hm... ``` $ WAYLAND_DEBUG=1 build/hyprpaper 2>&1 | rg viewpo [3289227.537] [email protected](12, "wp_viewporter", 1) [3289227.539] -> [email protected](12,...
That's weird that binding wp-fs changes the semantics of wp-vp. Might be worth opening an issue at wayland-protocols for clarification. > ``` > [3289274.831] -> [email protected]_destination(1919, 1079) > [3289289.401] ->...
> AFAIK with scaling you should only use the destination, as no cropping is needed. Can't say I fully understand their reasoning in the spec, though. Apparently set_source is optional...
After https://github.com/hyprwm/Hyprland/commit/859d6b9b8a961669c814632bbc7a1a9d94556551 something different happens:  (The top uses `set_buffer_scale(2)`, the bottom uses viewporter)
This is not even related to fractional scaling. The client may not even bind wp-fs, receive "scale=2" event, render with scale of 2 and instead of setting "buffer_scale=2" the client...
> Hyprpaper uses wp-fs-v1 and works And it is wrong. > ``` > [3289274.831] -> [email protected]_destination(1919, 1079) > [3289289.401] -> [email protected]_destination(1919, 1079) > ``` > This still seems wrong because...
I guess this can be done with a protocol version bump? "If version N or grater is bound, the set may be empty".
Test client: https://github.com/MaxVerevkin/river-kbd-layout-watcher