https://bugs.kde.org/show_bug.cgi?id=469192
--- Comment #21 from Nate Graham <n...@kde.org> --- (In reply to Sergio from comment #19) > I understand your point. > > I have also started using the Wayland session that does not show this > specific issue. Unfortunately, we are still in a trade-off phase, where one > needs to decide whether the Wayland troubles are better than the X11 > troubles or the other way round. ... and there seems little that can be done > on the KDE side. On the contrary, Plasma's wayland session is improving rapidly, while its X11 session is frozen in stone, never to get any better ever again. The same is true of the X server upstream. > In fact, most of the trouble I am experiencing with wayland seems to come > from: > > - the total lack of standardization of common things in Wayland Sounds like it's time for you to submit some Wayland protocols to fix this. :) > > - why cannot there be a standard way to do session restore so plasma > cannot do it? It's still a work in progress; see https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/18. Once that's accepted, we'll add support for it. > - why cannot there be a cross-toolkit env variable to decide if > applications should use X11 or Wayland and every toolkit has its own way, so > launching applications via `ssh -X` which should work just fine using > Xwayland does never work? Because there are multiple toolkits and they never came to an agreement about a common environment variable to use. This sounds like it could be a good candidate for a new Wayland protocol. > - why isn't there a single cross-toolkit env variable to control scaling? See above. But why is this needed? App developers don't need it because they just need to follow the wayland scaling protocols. So the only people who would use it are users, but then it should also not be needed since your DE of choice should take care of setting up the scaling infrastructure properly for all kinds of apps. If it doesn't, it's an issue with the DE. > - why Java applications won't obey scaling anyway so big commercial > applications (MATLAB to mention one) are now almost unusable unless you use > weird hacks like passing them through Xpra? Without knowing which apps, I can't answer that question, but I suspect based on other scaling-related questions that your system is misconfigured based on old habits from X11 that aren't translating to a Wayland world. > > - rather strange policy decisions > > - why can we have scaling only by 75-100-125-150 etc., what was the > issue with specifying DPIs that enabled a much finer tuning; You can set any scale value you want in the relevant KDE system settings page, not just multiples of 25%. > - why scaling is managed in a so weird way that most application > developers cannot deal with it, so that even a healthy and rapidly developed > project like libreoffice still has broken scaling on multi monitor with the > QT VCLs? LibreOffice with the QT VCL works just fine for me with a multi-monitor system where one monitor has 225% scale and another has 110% scale; I was using it this way just today. If it's not working for you, it sounds like your system is misconfigured. > - why cannot applications decide their own icon, so a lot of stuff > remains with the generic "W" icon and Qt's `setWindowIcon` has been broken > *by policy*? I think you just answered your own question. But there is a draft Wayland protocol that would implement this functionality: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/269 > - why is there no standard way to deal with the system tray, so those > developing for flatpack have such a hard time making icons appear there? To > mention a few, `sleek`, `spotube`, many other flatpacks applications cannot > show the tray icon on Wayland/KDE and some of these applications had to go > back to using X11 to be usable on plasma (spotube). This isn't an X11/Wayland thing; there *is* a standard way to set a System Tray icon and KDE implements it. -- You are receiving this mail because: You are watching all bug changes.
