Change almost all other uses of qrand() to QRandomGenerator

The vast majority is actually switched to QRandomGenerator::bounded(),
which gives a mostly uniform distribution over the [0, bound)
range. There are very few floating point cases left, as many of those
that did use floating point did not need to, after all. (I did leave
some that were too ugly for me to understand)

This commit also found a couple of calls to rand() instead of qrand().

This commit does not include changes to SSL code that continues to use
qrand() (job for someone else):
  src/network/ssl/qsslkey_qt.cpp
  src/network/ssl/qsslsocket_mac.cpp
  tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp

Change-Id: Icd0e0d4b27cb4e5eb892fffd14b5285d43f4afbf
Reviewed-by: Lars Knoll <lars.knoll@qt.io>

1 files changed, 4 insertions, 5 deletions

diff --git a/examples/widgets/doc/src/elasticnodes.qdoc b/examples/widgets/doc/src/elasticnodes.qdoc
index 09ac891b24..65e1195121 100644
--- a/examples/widgets/doc/src/elasticnodes.qdoc
+++ b/examples/widgets/doc/src/elasticnodes.qdoc
@@ -424,9 +424,8 @@
     \section1 The main() Function
 
     In contrast to the complexity of the rest of this example, the \c main()
-    function is very simple: We create a QApplication instance, seed the
-    randomizer using qsrand(), and then create and show an instance of \c
-    GraphWidget. Because all nodes in the grid are moved initially, the \c
-    GraphWidget timer will start immediately after control has returned to the
-    event loop.
+    function is very simple: We create a QApplication instance, then create and
+    show an instance of \c GraphWidget. Because all nodes in the grid are moved
+    initially, the \c GraphWidget timer will start immediately after control
+    has returned to the event loop.
 */