swww icon indicating copy to clipboard operation
swww copied to clipboard

query returns wrong info

Open WhyNotHugo opened this issue 2 years ago • 6 comments

swww reports wrong dimensions:

> swww query
DP-2 = 4586x1920, currently displaying: color: 000

Sway reports the correct sizes:

> swaymsg -t get_outputs
Output DP-2 'Ancor Communications Inc ROG PG348Q #ASMuhJCcVsHd' (focused)
  Current mode: 3440x1440 @ 59.973 Hz
  Position: 0,0
  Scale factor: 1.500000
  Scale filter: linear
  Subpixel hinting: unknown
  Transform: normal
  Workspace: 2 2:二
  Max render time: off
  Adaptive sync: disabled
  Available modes:
    3440x1440 @ 59.973 Hz
    3440x1440 @ 49.987 Hz
    1024x768 @ 60.004 Hz
    800x600 @ 60.317 Hz
    640x480 @ 60.000 Hz
    640x480 @ 59.940 Hz

Output eDP-1 'Sharp Corporation 0x148B Unknown' (inactive)
  Available modes:
    3840x2160 @ 59.997 Hz

WhyNotHugo avatar Oct 04 '22 16:10 WhyNotHugo

Thanks for the report! Could you please confirm whether the problem remains if you set the scale factor to a whole number? Also, does the image look particularly bad / distorted / cropped, or is it working fine?

LGFae avatar Oct 07 '22 18:10 LGFae

Images render fine, no distortion or anything. A 3440x1440 image fits perfect.

WhyNotHugo avatar Oct 13 '22 18:10 WhyNotHugo

$ swww query
eDP-1: 1504x1002, scale 2, currently displaying color: 000
$ hyprctl monitors
Monitor eDP-1 (ID 0):
        [email protected] at 0x0
        scale: 1.50

Note that swww is seeing a different scale value that hyprctl. This seems to be because Wayland only allows the communication of integer scales: for a scale of 1.5, Hyprland tells client programs about the real scaled resolution (2256x1504 by 1.5 gives 1504x1002), then gives them an integer scale (1.5 is 3/2, so 2.0). As such, the actual unscaled monitor resolution is simply not known to swww. I don't think anything can be done about this.

thedmm avatar Jan 29 '23 14:01 thedmm

The issue isn't just fractional scaling tho.

3440x1.5 is 5160, not 4586.

WhyNotHugo avatar Feb 24 '23 14:02 WhyNotHugo

But I'd ignore this until #91 is implemented.

WhyNotHugo avatar Feb 24 '23 14:02 WhyNotHugo

I believe #290 fixes this.

LGFae avatar Apr 20 '24 17:04 LGFae