Email or username:

Password:

Forgot your password?
Top-level
:yell: Ibly 🏳️‍⚧️ θΔ

@marcan ah, that actually explains to me why X development has slowed down, now i know!

hoping wayland eventually gets the support for my favorite music players that still don't work... or more accurately have it go vice versa. if that doesn't happen maybe i'll start writing my own damn winamp 2.x-compatible music player lol

10 comments
Hector Martin

@EeveeEuphoria How does a music player not work? It's a client, it should work in XWayland...

:yell: Ibly 🏳️‍⚧️ θΔ

@marcan audacious, qmmp, and probably xmms use funny windows when they're using winamp skins, since that's how winamp works

the funny windows meaning it's like, 3 windows that can be moved together, which works as intended in X, but not in wayland. in wayland it just... doesn't work, and often spawns the windows in random places, and doesn't let you move all 3 windows at the same time when they're stacked.

i'm guessing it's either (X)wayland doing something wrong, or the programs just using a deeper layer of X that xwayland doesn't implement

@marcan audacious, qmmp, and probably xmms use funny windows when they're using winamp skins, since that's how winamp works

the funny windows meaning it's like, 3 windows that can be moved together, which works as intended in X, but not in wayland. in wayland it just... doesn't work, and often spawns the windows in random places, and doesn't let you move all 3 windows at the same time when they're stacked.

:yell: Ibly 🏳️‍⚧️ θΔ

@marcan really the windows do render, and you can still move them around, it's just that it doesn't work all that well.

audacious is the best music player out of all 3, and last i checked (around 6-ish months ago) it still had that issue unfortunately :/

i could use it without winamp skins, but i made a xenia the fox skin for it and i'm not gonna let that go to waste

:yell: Ibly 🏳️‍⚧️ θΔ

@marcan i just relogged in to wayland to check, and it's worse than i remembered, audacious simply won't let me move the windows at all!

so uh yeah, kinda unusable like that, unfortunately.

Hector Martin

@EeveeEuphoria Ah yeah, Wayland is sort of designed not to give control over screen placement to the individual windows... I think XWayland gets some special privileges there, but not all. This is mostly for good reasons (it abstracts out what a screen is and how it works, so clients don't have to worry about things like complex mixed-DPI multi-monitor desktops where there isn't even a single pixel coordinate system), but it does break fancy hacks like the ones you mention, unfortunately.

:yell: Ibly 🏳️‍⚧️ θΔ

@marcan dang, that sucks. the only thing i might know of that might work is the webamp desktop client, since i know that thing takes up the whole screen (my window closing effect is that classic fire effect, and whenever webamp closes, my whole screen is on fire, meaning that's how it achieves that)

Hector Martin

@EeveeEuphoria Yeah, a single transparent window with internal subwindow management is *probably* the way to go on Wayland, though I'm not a Wayland window management expert. It's a tricky problem.

:yell: Ibly 🏳️‍⚧️ θΔ

@marcan yeah, that might be the way to go. as it stands, audacious and QMMP have their developers both essentially saying "we won't support wayland", with QMMP specifically saying wayland doesn't have the right feature set to fix the winamp skin mode

Hector Martin

@EeveeEuphoria Yeah, it's one of those things where Wayland and X are just different. Some things you can do in Wayland and not X, some things you can do in X and not Wayland (or at least not well/easily)... at the end of the day we have to accept that they're different and we lose some things and gain some things.

Charlotte 🦝 θΔ

@EeveeEuphoria @marcan Not sure where you are getting that audacious bit from tbh, I am running audacious natively on wayland right now. Maybe only the winamp skin mode?

Go Up