News for hackers. Stuff that matters.
Re:HW accelerated Xwayland rendering for Nvidia merged by michaelmrose on Friday April 09, 2021 @03:00PM (#26754618)
Logically you would just put the same dock on both monitors and tell it to move all new windows to DP-2 (or wherever), open an issue on their bug tracker asking for this feature to be reinstated and explaining why, and move on. This wouldn't so much be a hacky workaround as using a built in feature that achieves the same result.

In my opinion primary monitor is conflating 2 settings that perhaps ought to both exist in an easier to use that windows rules.

Open new windows on ____ selected from monitor with mouse cursor, same window as focused application, a selected monitor with the default being same monitor as focused application.

Always show panel in place of any other bar yes/no. Unchecked by default. You can have a panel on each monitor and put things of your choosing in each panel or even have a panel on top and below on the same monitor if you like. So what happens if you have a panel on your primary monitor 1 and also on your secondary monitors 2 and 3? Say you unplug the laptop and monitor 3 becomes the only monitor.

The most obvious and simple thing would be to show the same things on all 3 including showing a taskbar for the windows just on that particular monitor so that when you undock you can still do the same things. Windows does this for example the only difference is which bar has the tray.

The most theoretically correct would seem to be allowing you to set different bars for different configurations but this would be complicated and perhaps little used.

What I've suggested would be to give you the ability to set a primary bar that is always displayed hiding any secondary bars that normally appear on that display.

Re:HW accelerated Xwayland rendering for Nvidia merged by CarelessExpert on Friday April 09, 2021 @03:11PM (#26754778)
> This wouldn't so much be a hacky workaround as using a built in feature that achieves the same result.

But there's already a built-in feature in KDE/X11 for this. It's just broken in Wayland. It's a feature regression, plain and simple.

Re:HW accelerated Xwayland rendering for Nvidia merged by michaelmrose on Friday April 09, 2021 @03:32PM (#26755025)
So ask them to put it back?
Re:HW accelerated Xwayland rendering for Nvidia merged by CarelessExpert on Friday April 09, 2021 @03:35PM (#26755070)
I think you're missing the entire point of my comment.

I'm not saying these things can't be resolved! They probably will be, eventually. I have every confidence that some day, KDE on Wayland will restore this now-missing feature.

I'm simply saying, through my personal laundry list of bugs and regressions, that Wayland is a long way off from ready for prime-time due to a wide range of issues that go well beyond the oft cited, very well-trod issue of the lack of screen sharing.

That's it.

And I genuinely look forward to the day those gaps are closed and I can use Wayland full time!

I just have a feeling that won't be until 2023 at the earliest.

Re:HW accelerated Xwayland rendering for Nvidia merged by craftinator on Friday April 09, 2021 @04:53PM (#26756014)
I'm pretty sure Wayland is never the problem, it's always the user. If no one used Wayland, it would run exactly as designed!
Re:HW accelerated Xwayland rendering for Nvidia merged by michaelmrose on Friday April 09, 2021 @04:45PM (#26755910)
I have a feeling it will be 20never as I sit in front of my machine running i3wm version whatever in 2029.