Conversation
|
reqs a wiki update ofc ass well |
Unfortunately, I believe |
|
@q234rty as far as I know, the patches don't solve this issue either. |
|
@fufexan These patches partially mitigate this issue by letting the compositor do per-monitor downscaling, e.g. if one monitor is under 200% and another monitor is under 100%, Xwayland apps will see two 200% screens and the compositor will do the downscaling on the 100% monitor. This is of course not perfect but still much better than having very large Xwayland apps on the 100% monitor. |
|
@q234rty if the users desire that functionality, they can copy the code previous to these commits and override hyprland themselves. In the meantime, we will be waiting for an official solution. |
|
Whatever, I will just continue maintaining my AUR hyprland-hidpi-xprop-git package with the old approach :) |
|
we are removing the patches because of my pressure to do so. The approach is shit and buggy, requires patching which already is a pain, and xwayland:force_zero_scaling does exactly the same. |
As mentioned above, |
|
does it not? how so? it removes scaling. |
|
Yes, it removes scaling by the compositor, but no, X11 itself does not handle multi monitor with different scale factors, so letting X11 see the same scale factor across all monitors and letting the compositor do the downscaling is helpful, which is what the old approach did. |
236f770 to
6aa2cdd
Compare
spikespaz
left a comment
There was a problem hiding this comment.
I left a many comments, most are nitpicks or questions. This looks good as it is. There are some suggestions that do not align with the description of the PR.
- remove `hidpiXWayland` option - rename `nvidiaPatches` -> `enableNvidiaPatches` for consistency
It seems that, on NixOS at least, having both the Hyprland and the wlr desktop portals does not result in unexpected behaviour. xdph will be started and wlr ignored.
Describe your PR, what does it fix/add?
hidpiXWaylandoptionnvidiaPatches->enableNvidiaPatchesfor consistency withenableXWaylandIs there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Will need to be announced to the community when merged.
Is it ready for merging, or does it need work?
Ready.