Remove warning from QColor::setNamedColor().
This warning is pointless as the user can anyway check if the color is valid after making the call by calling isValid(). Using isValidColor() could be used but it has a big performance overhead as validation then needs to be done twice. Task-number: QTBUG-19098 Reviewed-by: Erik Verbruggen (cherry picked from commit a423ff5474b89028eeca95b254f5184311c8223b)bb10
parent
4ec4d78711
commit
0377b7f96d
|
|
@ -532,8 +532,7 @@ QString QColor::name() const
|
|||
|
||||
void QColor::setNamedColor(const QString &name)
|
||||
{
|
||||
if (!setColorFromString(name))
|
||||
qWarning("QColor::setNamedColor: Unknown color name '%s'", name.toLatin1().constData());
|
||||
setColorFromString(name);
|
||||
}
|
||||
|
||||
/*!
|
||||
|
|
|
|||
|
|
@ -1506,7 +1506,6 @@ void tst_QColor::setallowX11ColorNames()
|
|||
for (int i = 0; i < x11RgbTblSize; ++i) {
|
||||
QString colorName = QLatin1String(x11RgbTbl[i].name);
|
||||
QColor color;
|
||||
QTest::ignoreMessage(QtWarningMsg, QString("QColor::setNamedColor: Unknown color name '%1'").arg(colorName).toLatin1());
|
||||
color.setNamedColor(colorName);
|
||||
QVERIFY(!color.isValid());
|
||||
}
|
||||
|
|
@ -1528,7 +1527,6 @@ void tst_QColor::setallowX11ColorNames()
|
|||
for (int i = 0; i < x11RgbTblSize; ++i) {
|
||||
QString colorName = QLatin1String(x11RgbTbl[i].name);
|
||||
QColor color;
|
||||
QTest::ignoreMessage(QtWarningMsg, QString("QColor::setNamedColor: Unknown color name '%1'").arg(colorName).toLatin1());
|
||||
color.setNamedColor(colorName);
|
||||
QVERIFY(!color.isValid());
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in New Issue