f_ changed the topic of #wayback to: Wayback - a wayland-based X11 environment | https://wayback.freedesktop.org/ | preview release 0.1 is out! https://wayback.freedesktop.org/news/2025/07/23/wayback-0.1-released/ | src: https://gitlab.freedesktop.org/wayback/wayback | logs: https://libera.catirclogs.org/wayback | matrix bridge: #wayback:catircservices.org
grufwub has quit [Remote host closed the connection]
grufwub has joined #wayback
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #wayback
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #wayback
norwoodites has joined #wayback
pinskia has quit [Ping timeout: 260 seconds]
britney has quit [Quit: WeeChat 4.6.3]
britney has joined #wayback
jvvv has quit [Quit: WeeChat 4.7.0]
norwoodites has quit [Read error: Connection reset by peer]
pinskia has joined #wayback
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #wayback
remotethink has joined #wayback
<remotethink> sup
remotethink has quit [Remote host closed the connection]
mojo_x has joined #wayback
mojo_x has quit [Client Quit]
mojo_x has joined #wayback
__0x1eaf has joined #wayback
panekj has quit [Quit: bah]
panekj has joined #wayback
mojo_x has quit [Ping timeout: 248 seconds]
panekj has quit [Quit: bah]
panekj has joined #wayback
panekj has quit [Client Quit]
panekj has joined #wayback
tomate3 has joined #wayback
vkareh has joined #wayback
tomate has quit [Ping timeout: 272 seconds]
tomate3 is now known as tomate
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #wayback
__0x1eaf has quit [Quit: Lost terminal]
ConanKudo[m]1 has quit [Quit: Idle timeout reached: 172800s]
<f_> I'm writing the 0.2 blogpost
<f_> also I'll make a few adjustments to the website as you asked Son_Goku
ConanKudo[m]1 has joined #wayback
<ConanKudo[m]1> f_: thanks
<f_> you're welcome. Thanks for handling my version MR while I was sick :)
Achill[m] has quit [Quit: Idle timeout reached: 172800s]
__0x1eaf has joined #wayback
satvoim has joined #wayback
satvoim has left #wayback [Leaving]
<bigmac> Hey. I am currently looking into #11. Could I ask if setting xorg to lower dpi, or higher dpi should be prefered when the amount of outputs with a Y scale factor is the same as say Y+1 where Y is the highest scale factor there is on the system? An example of this is having two monitors, one low res and one high res
<Wayback> #11 properly notify Xwayland about screen DPI (https://gitlab.freedesktop.org/wayback/wayback/-/issues/11) [opened]
<bigmac> Y+1 would be the biggest scale factor on the system* but I hope the example makes it clear
<f_> In other news, site!3
<Wayback> site!3 content/news: 0.2 announcement (https://gitlab.freedesktop.org/wayback/wayback.freedesktop.org/-/merge_requests/3) [opened]
<f_> ConanKudo[m]1: ^ also adds /news to the navbar and makes it show only one entry on the homepage
__0x1eaf has quit [Quit: Lost terminal]
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #wayback
<f_> bigmac: I'd either do Y for both, or Y+0.5 somehow
<bigmac> f_: Hm, so to prioritize the lower option. Are you aware of what xorg prioritizes if such situation occurs?
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #wayback
<f_> am not
<f_> I am not*
<bigmac> Finding a compromise would be fine, until the differences are way too high I would think
<f_> Xorg doesn't properly do per-screen DPI in any case.
<bigmac> The global default is 96, but we could skim through the outputs and find a better suiting number. I am thinking about the edge cases and yeah,.. it probably will not play out nicely if one has a 4K monitor and a little tablet-like screen plugged in at the same time. If we were to compromise in a way of finding the mid point between all the factors, we would be probably left with two unusable
<bigmac> screens
mojo_x has joined #wayback
mojo_x has quit [Changing host]
mojo_x has joined #wayback
vkareh has quit [Quit: WeeChat 4.7.0]
f_|cat has joined #wayback
<f_|cat> <bigmac> The global default is 96, but we could skim through the outputs and find a better suiting number. I am thinking about the edge cases and yeah,.. it probably will not play out nicely if one has a 4K monitor and a little tablet-like screen plugged in at the same time. If we were to compromise in a way...
<f_|cat> Maybe a switch to disable that thing would be nice.
<bigmac> To go back to the hard coded default? Yeah, agreed
<f_> yep
<f_> Or have a switch to explicitely enable it?
mojo_x has quit [Ping timeout: 272 seconds]
<bigmac> anyhow x apps don't really seem to respect the "custom" DPI. Some programs, such as the i3bar and i3 wm interface in general, are fine, but the terminals I am trying are just ignoring it altogether. On icewm, for example, the time indicator and on hover titles scale, but the rest of the ui does not.. Is -dpi not *the* flag to set dpi with?
<f_> it's called dpi so I'd say yes
<bigmac> f_: Just out of curiosity, could you try this: https://paste.centos.org/view/8f61f83a and see how reliably it scales everything up with which ever xwm you're using? You might want to make it more like 150, but since I am uisng a macbook with a retina screen I need it to be at around that number.
<f_|cat> yeah sure, give me a sec