Bug 336662 - Poor rendering quality of hovered tab thumb outline effects
Summary: Poor rendering quality of hovered tab thumb outline effects
Status: REOPENED
Alias: None
Product: QtCurve
Classification: Frameworks and Libraries
Component: qt5 (other bugs)
Version First Reported In: git
Platform: unspecified Linux
: NOR minor
Target Milestone: ---
Assignee: Yichao Yu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-24 14:27 UTC by Eike Hein
Modified: 2021-03-09 07:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Hovered tab thumb in QtCurve+Breeze (2.10 KB, image/png)
2014-06-24 14:27 UTC, Eike Hein 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Eike Hein 2014-06-24 14:27:16 UTC 
The thin dark outline around hovered tab thumbs becomes too bright in the corners, giving a frazzled appearence. Likely due to poor sampling in anti-aliasing. Screenshot coming.

Reproducible: Always
Comment 1 Eike Hein 2014-06-24 14:27:32 UTC 
Created attachment 87374 [details]
Hovered tab thumb in QtCurve+Breeze
Comment 2 Andrew Lake 2014-06-28 16:19:03 UTC 
While the visuals are as described, the difference between what it looks like and what it perhaps should look like is barely discernible. While arguably not technically ideal, the hovered tab is remains clearly discernible as a hovered tab and functions as it should. Not a critical issue. It could be addressed either by fixing the issue in QtCurve or when a C++ implementation of the reference UI controls design becomes available for QWidget-based applications.

Leaving open as needs info until the underlying QtCurve issue is identified.
Comment 3 Eike Hein 2014-07-23 20:57:42 UTC 
We're upstream now, reopening.
Comment 4 Eike Hein 2014-07-23 20:59:19 UTC 
Resetting assignee.
Comment 5 Justin Zobel 2021-03-09 07:30:29 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.