Gregory's Server@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.
|
5 comments
 @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.  @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 @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.  @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? |
@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)