Bug 401174

Summary:	Flickables should be pixelAligned by default
Product:	[Frameworks and Libraries] frameworks-kirigami	Reporter:	Fabian Vogt <fabian>
Component:	general	Assignee:	Marco Martin <notmart>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate
Priority:	NOR	Keywords:	usability
Version:	unspecified
Target Milestone:	Not decided
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=393202 https://bugs.kde.org/show_bug.cgi?id=400052
Latest Commit:	https://cgit.kde.org/kirigami.git/commit/?id=508236f2df2458c53c07bcb3e83e06a6b5c7d332	Version Fixed In:	5.53

Description Fabian Vogt 2018-11-18 18:36:09 UTC

Text at non-integer X/Y coordinate is missing a few pixels at the top and practically unreadable.

I'm not sure whether there's a Qt bug report, but I was unable to come up with a minimal reproducer.

Just by scrolling in any Kirigami.ScrollView with a touchpad, all of the text inside becomes unreadable. Setting pixelAligned using gammaray fixes it.

Comment 1 Nate Graham 2018-11-19 20:53:12 UTC

See slso Bug 393202 and Bug 400052. Do you think any of these are duplicates of each other?

*** This bug has been marked as a duplicate of bug 393202 ***

Comment 2 Fabian Vogt 2018-11-19 21:00:09 UTC

(In reply to Nate Graham from comment #1)
> See slso Bug 393202 and Bug 400052. Do you think any of these are duplicates
> of each other?
> 
> *** This bug has been marked as a duplicate of bug 393202 ***

pixelAligned: true will likely fix Bug 393202, but I don't think the labels in Bug 400052 are in a Flickable. It might be the same "y: foo+0.5" issue though.

Comment 3 Nate Graham 2018-11-26 14:19:15 UTC

Fixed along with the fix for Bug 393202.