Done automatically with clazy static analyzer.

Change-Id: Ia0cf8fa24331ab102a3c3c30c2aa92ef1ba772e2
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

We need it in 3 places in qtdeclarative and we could also use it in
QtCreator. We don't want to bundle it with the debug client code as it
is also necessary for the server.

QPacket replaces QQmlDebugStream as it has the same purpose. This
also fixes the inconsitent handling of data stream versions.

Change-Id: I650fae353f267511c551b427d9169f4d718aa7f2
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

Change-Id: I11ea57222ba5aa683b7bfd7735fbc1d2cf86e875

Before we used Qt::OtherFocusReason for normal key navigation, such
as up/down/left/right. But in style world, the reason is critical
for focus change.

Now we follow the way in widgets world, use Qt::TabFocusReason and
Qt::BacktabFocusReason for down/up and right/left(or reversed if
mirrored).

Task-number: QTBUG-41801
Change-Id: I99e97ea4ced2cef9b3280c578c3a463de8fe1727
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>

Make the distinction between connectors and services a bit clearer.

Change-Id: I5a8de587beaaed4b4b2138d9d50c5b92fea38df9
Reviewed-by: Ulf Hermann <ulf.hermann@theqtcompany.com>

Just not requesting a depth buffer is insufficient since there's nothing
guaranteeing that the EGL or other implementation will return depthless
configs. When the depth buffer is always there, setting the environment
variable is futile. To do what the user has requested, the value has to
be checked in the renderer too.

Change-Id: I1f572bc6f2f5b5aa94070a239d6e871e3421a51f
Reviewed-by: Louai Al-Khanji <louai.al-khanji@theqtcompany.com>
Reviewed-by: Gunnar Sletta <gunnar@sletta.org>

Change-Id: I63728b127d196d692f42b096e670ea0a3e336968
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

Change-Id: I034fa0093aa6dad41c2566a8c7ef8fba9e7d4b82
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

Use character literals where applicable.

Change-Id: I294fc4cb5cbbd23df9735ba2b398118f37cbe08a
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

QML text rendering elements have a renderType property controlling
whether to use 'Qt' rendering or 'Native' rendering.  There is no reason
to mix different types of rendering in one static ui.  The element-local
properties may be used to change the rendering type during animation
for example, but otherwise there should be an application-wide rendering
mode for text.

That means that all Text-based elements in QML should default to the
same rendering mode.  Additionally, applications wishing to use
NativeRendering, wish to use it for all text-based elements, so they
require changing the defaults of the elements themselves, still allowing
the possibility of changing the rendering mode during animation.

Creating third party wrappers for each of the QML text rendering types
is not a solution because an application requires the same font
rendering for all text.

That is, whether written directly with QML Text* elements, or using
QtQuick controls, or another 3rd party component set, it is necessary to
set the same font rendering mode for all text, except in temporary
execptional cases.

The known options to achieve this are

 1) Create an environment variable to set the default rendering.
 2) Add C++ API to set the default
 3) Add a build-time option to set the default.

The first option is unsatisfying because it is fragile and is easy to
get wrong.

The second option is incomplete because it does not affect qmlscene etc,
so it would require adding a command line argument to qmlscene to change
the default.  That is unsatisfying because it is also fragile.  It is
necessary for the sanity of developers and designers (and also end
users) that qmlscene use the correct default by default.  It must be
easy to create qml files for designers to run with qmlscene and which
look correct.

The third option is the one chosen for this patch.  It is most suitable
for environments where the Qt build and settings are contained because a
particular Qt build is shipped with the application using it (This is
the most common way Qt is used).  It affects all uses of the text
rendering elements, whether used through qmlscene or through another
entry point, and it allows changing the property in QML code away from
the build-time-determined default.

When building Qt, -DQT_QUICK_DEFAULT_TEXT_RENDER_TYPE=NativeRendering
may be passed to configure to affect the default rendering for the Qt
build.

It also leaves the question why the default text rendering is 'Qt'
instead of being 'Native', given that many of the Qt controls need to
switch to Native anyway (though this depends on the platform and the
style).

Change-Id: Ib0eed61caf4895b29e5c05e0418fad9962779f85
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>