From 180ee8a8de459b752f739e1a9d56d271303d0302 Mon Sep 17 00:00:00 2001
From: Andy Shaw <andy.shaw@digia.com>
Date: Mon, 9 Mar 2015 12:34:38 +0100
Subject: Explicitly cast to a uint to fix a compile error

When using QtTest inside the notification example for QtAndroidExtras
there as a problem with the compilation as it saw it as being an ambiguous
check. Therefore doing an explicit case to uint ensures it is not a
problem.

Change-Id: Ibc9ce4c64292bf5ae7c501c592d8c42a66934b8b
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
---
 src/testlib/qtestmouse.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/testlib')

diff --git a/src/testlib/qtestmouse.h b/src/testlib/qtestmouse.h
index 0b27537ae4..f29db926a4 100644
--- a/src/testlib/qtestmouse.h
+++ b/src/testlib/qtestmouse.h
@@ -98,7 +98,7 @@ namespace QTest
             mouseEvent(MouseRelease, window, button, stateKey, pos);
             return;
         }
-        QTEST_ASSERT(stateKey == 0 || stateKey & Qt::KeyboardModifierMask);
+        QTEST_ASSERT(uint(stateKey) == 0 || stateKey & Qt::KeyboardModifierMask);
 
         stateKey &= static_cast<unsigned int>(Qt::KeyboardModifierMask);
 
-- 
cgit v1.2.3