https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #46 from Callegar <[email protected]> --- All your points are indeed valid. As a matter of fact, I used a conditional precisely because cons might outweight pros, but I thing that an evaluation thereof can be useful. - On one hand: for anyone even a bit knowledgeable it should be quite easy to set env variables to have the preferred VCL as a default on their own machine. Most distros ease that by per-arranging a config file for that (e.g., in arch you get a pre-filled `/etc/profile.d/libreoffice-fresh.sh` where you just need to uncomment a line). - On the other hand: 1. many, many laptop now have a 3k or 4k resolution and even 2k laptops benefit from a 1.25 scaling factor when they have 10.2", 11" or even 12" screens. Whenever these laptops get docked, you'll likely run into the issue. Most people who use laptops professionally dock them as soon as they have the possibility to do so, for ergonomics, productivity and - may seem weird - saving the laptop surface from getting stained on the palms zone. The setup is specific, but by no means rare. 2. The issue is not serious in itself, but is extremely visible as something that "explodes in your face" as soon as you start the application. Very bad on a marketing perspective, IMHO. 3. the workaround for the issue is easy but definitely not easily discoverable. Having a "tip" for it might be useful, but from a marketing perspective it is bad to have tips about known issues. 4. Most users do not even know what a VCL is. Users asking for QT VCLs probably represent the subset of users knowledgeable enough to set the SAL_VCL_PLUGIN env variable. 5. I may be wrong, but I am getting the impression that either: the issue is not easily fixable or the developers working on the QT VCL have more urgent tasks at this time (QT6, probably), so the issue is to stay for some time. During this time, point 1. can only get worse. 6. Applications that work well out of the box on gnome, but not on KDE may unfortunately cast a bad shade on the whole of KDE. Personally, I do not care that much, since I am among the user-set knowing `SAL_VCL_PLUGIN`, but I wonder about the less knowledgeable group. -- You are receiving this mail because: You are the assignee for the bug.
