- User Since
- Feb 17 2015, 6:21 PM (261 w, 4 d)
Mon, Feb 3
You may want to look at the DBus part of this with dfer-monitor, a tool I have written. It is especially useful for looking at latency problems.
Jan 21 2020
@fvogt Yeah thanks, that made more sense than you spoon-feeding me the information for the commit message ;)
Jan 16 2020
So what do we do here? The Qt bug has been fixed but still I'm not sure what should be done about the environment variables.
Dec 29 2019
Dec 28 2019
It's probably okay to still say that scaling is enabled "in general" but for scaling <2, and why not, maybe even greater, hinting should not be inhibited. The screen is still made of pixels. Qt is not going to be able to throw out all the hinting and subpixel code like Apple did, because it still needs to be supported for non-Retina screens anyway, for a long time. I'll open a Qt bug and see how it goes.
I think I see the problem. You pay for the possibility to have scaling with unhinted fonts. I am pretty sure that that isn't an acceptable way of handling it. Most Linux desktop fonts are intended to be used with some hinting (slight hinting usually?). QHighDpiScaling::isActive() returns true even when the scale factor is 1.0 as in my case. Looks like a Qt bug to me.
Dec 24 2019
Just to make this extra clear, I have nothing against auto-scaling. There is probably a KCM to set it however I want if I don't like the default. My problem is with blurry and in some cases ("-=") disfigured font rendering. That should never happen regardless of physical and logical DPI (though no subpixel rendering and maybe no hinting might be fine at >= 2.0 scaling). With this patch, it looks like with Qt 5.13 on not very high DPI screens, i.e. it looks nice. I don't own a really high DPI screen so far.
Dec 23 2019
Compiled against Qt 5.14 before this change:
Nov 28 2019
Oct 12 2019
Aug 22 2019
Apr 13 2019
Oct 31 2018
This fixes session restore for me.
Sep 27 2018
Sep 6 2018
Aug 30 2018
This change makes kwin_x11 crash on startup. Please fix kwin or degrade this to a warning.
Aug 3 2018
OK, I've tested it, the fix that this amends still works as well.
Aug 2 2018
@sandsmark , it would be good to retest if your fix still works after this. IIRC QApplication does not lazily initialize the event loop though.
Jul 23 2018
Jul 6 2018
Jun 8 2018
There are many more plain qDebug()s in this module, but this one seems to produce the most noise...
Mar 30 2018
Dec 18 2017
Nov 27 2017
Change base revision
Change second index check to >0
Nov 23 2017
Maybe it is better to return an empty string in this case but I don't know. Otherwise I might thave pushed this directly. In the case of my missing file, the returned string was the name of the folder <file_db_data>/00/, which generates an error message that the file it tried to open is actually a folder...