GitLab

Reviewed-by: Kai Koehne

Old logic was too fragile to maintain.
Now it's  PointMixed -> PointPlain -> RangeMixed -> RangePlain.

That means createComponent etc. will now be completed.

Now using an explicit Mode (generated, imported) instead of empty
or set filename convention. Just like in Html5App.

Some things forgotten as part of commit f9e65028 since
these files are not compiled together with Qt Creator.

Fixes compile of QML Observer and QMLJSDEBUGGER-enabled QtQuick
Applications.

AbstractFormEditorTool -> AbstractLiveEditTool
LayerItem -> LiveLayerItem
SelectionIndicator -> LiveSelectionIndicator
SelectionRectangle -> LiveSelectionRectangle
SelectionTool -> LiveSelectionTool
SingleSelectionManipulator -> LiveSingleSelectionManipulator
RubberBandSelectionManipulator -> LiveRubberBandSelectionManipulator

Task-number: QTCREATORBUG-2968
Reviewed-by: Alessandro Portale

Reviewed-By: Christian Kandeler

All type information should be now available.

Changing this field will not have an effect anyway.

All this environment setting was just an approximation of what the
"mad" script does better.

This simplifies the call and also fixes a bug along the way.

Task-number: QTCREATORBUG-3589

When closing the app via the WM the status of the services change
to 'not available'. We used to log this as an error to the debugger
log, causing the log to 'magically' pop up.

Reviewed-by: Christiaan Janssen

No need to add random '1' if there's only one.

We used to only fallback at start time from a invalid/empty setting
to the cmake in path. Now we do that even if the setting is later
edited.

Task-Nr: QTCREATORBUG-3739

The testing environment seems wrong. It works properly in the real FakeVim.

For this option it would actually be better to reapply the state of the
toggle button to the restarted QtQuick application rather than resetting
the state of the button.

* Renamed Toolbar to ToolBar
* Use mass-disconnect instead of duplicating all connect calls
* Split up setupToolbar(bool)

Task-number: QTCREATORBUG-3664