awavauatush @ninjawedding@sdfn-01.ninjawedding.org

@staticsafe recently they all sound like random Slashdot commenters

(I mean, for now, I can piece together what to do from SDL, but seriously, this is a mess. I don't care if you're on Team Client or Team Server, the developer experience sucks)

Look, but do not comment, on this: https://gitlab.gnome.org/GNOME/mutter/issues/217

I was trying to figure out why in the hell my Qt apps under Wayland had no window decorations. This appears to be entirely intentional behavior and there's code you need to write to negotiate server-side (i.e. compositor-provided) window decorations, and if you *can't* negotiate that you should provide your own decorations.

There are good arguments for doing this. I see it as the Vulkan equivalent of window management: we all need something different, so you get to put the pieces together yourself.

Where the hell is the code sample for "opt into xdg-decoration" though? That's all I really want.

@djsundog well then

{"type": "Invite", "target": [ { "type": "Fellowship" } ] }

@djsundog what if the token is the One Ring

@CharredStencil "Do not, my friends, become addicted to privacy. It will take hold of you, and you will resent its absence"

@hirojin thanks :P

it's kinda tempered though by the knowledge that all this literally just works on macOS

@maiyannah Ah! I missed the bit about the scaler; I also will need to go find that.

@maiyannah I thought TempleOS was locked to 640x480? Could be wrong; I haven't run it in a while.

The multimedia document shell thing *is* pretty spectacular, and it's a damn shame everything else is so far behind it.

last bit of hidpi kvetching for today:

GOOD: If you *can* get KDE working on Wayland, hidpi experience truly is much better -- "it's better on Wayland" isn't just a meme

BAD: KWin needed to set QT_WAYLAND_DISABLE_WINDOWDECORATION to disable QtWayland's window decorations, but QML ApplicationWindows aren't recognized by KWin (or something), so QML apps under Wayland don't get window decorations

(┛ಸ_ಸ)┛彡┻━┻

@maiyannah well, this is the sort of mess that only God Himself could sort out

"Pay what you want for the Humble Dystopian Bundle"

can I pay in water

@alex I don't think it's enough, but I put that instance on block anyway after I got three follows from there in quick succession, all from accounts with no posts

@cascode yep, KDE is Qt

Qt Creator mixes Qt Widgets and Qt Quick in various ways; Qt Quick was designed for variable pixel densities, Qt Widgets was not, and yet, ironically, Qt Widgets seems to cope better with variable pixel densities

@cascode i don't know what I find funnier, the shit font rendering or the layout goofs

lol

@er1n i guess the autoroaster could be relegated to the plugin system

on a related but much more positive note, Sven Neuhaus' DPI calculator (https://www.sven.de/dpi/) is a very useful tool

anyway I think I'm going to forcibly disable automatic scaling in jortjams, because the behavior is so opaque and counterintuitive on Linux and Windows. usually in this case I blame me, but I've never had this much trouble getting scalable UIs to work on iOS

if you know of a Linux software combo that handles pixel ratios > 1 with the same grace as macOS/iOS, please let me know

so, probably to no one's surprise, it turns out:

- scaling GUIs on xorg for different pixel densities is a trash fire
- "It's better on Wayland"

you can get pretty close, but it always seems like something's off, like a text field displaying 8pt text with 8px padding everywhere