Commit 33802cec authored by Boudewijn Rempt's avatar Boudewijn Rempt

Fix build on windows

And this is why qMax should be used, and not std::max.
parent 6bc9382e
......@@ -195,7 +195,7 @@ void KisFloatColorInput::update()
m_dblNumInput->setMaximum(maxVisibleFloatValue);
// ensure at least 3 significant digits are always shown
int newPrecision = 2 + std::max(0.0, std::ceil(-std::log10(maxVisibleFloatValue)));
int newPrecision = 2 + qMax(0.0, std::ceil(-std::log10(maxVisibleFloatValue)));
if (newPrecision != m_dblNumInput->decimals()) {
m_dblNumInput->setDecimals(newPrecision);
m_dblNumInput->updateGeometry();
......
......@@ -91,7 +91,7 @@ KisToolPaint::KisToolPaint(KoCanvasBase * canvas, const QCursor & cursor)
int brushSize = 1;
do {
m_standardBrushSizes.push_back(brushSize);
int increment = std::max(1, int(std::ceil(qreal(brushSize) / 15)));
int increment = qMax(1, int(std::ceil(qreal(brushSize) / 15)));
brushSize += increment;
} while (brushSize < maxSize);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment