Update QPalette() documentation to not mention the application palette
It's an implementation detail that the default constructed palette happens to use the d-pointer of the application palette, and as a result has the same colors as the application palette if requested. The palette has an empty resolve mask, and hence all the colors in the palette are undefined. Users should not rely on QPalette() to represent the application palette when for example overriding a parent palette. Task-number: QTBUG-85226 Change-Id: Ia6747887eef6e9a5f21b2002066608c433260de2 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Paul Wicking <paul.wicking@qt.io> Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> (cherry picked from commit 74559dccc84ed0f0f7d8f57165fe387c3e112485) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
parent
80bcba5661
commit
908bfa7782
@ -530,7 +530,10 @@ static void qt_palette_from_color(QPalette &pal, const QColor &button)
|
||||
*/
|
||||
|
||||
/*!
|
||||
Constructs a palette object that uses the application's default palette.
|
||||
Constructs an empty palette object with no color roles set.
|
||||
|
||||
When used as the palette of a QWidget the colors are resolved
|
||||
as described by QWidget::setPalette().
|
||||
|
||||
\sa QApplication::setPalette(), QApplication::palette()
|
||||
*/
|
||||
|
Loading…
x
Reference in New Issue
Block a user