Note that according to QSettings design, the file itself then is
in $CREATORDIR/share/qtcreator/Nokia/QtCreator.ini. Note case (Unix)
and Vendor dir!

* Add a new base class to derive build- and runconfigurations as
   well as buildsteps from.

Reviewed-by: dt

They do what you expect them to do, that is build only a subtree.
The implementation is a little bit strange. We temporarly set the sub
node to be built on the BuildConfiguration, enqueue that
BuildConfiguration (which calls BuildStep::init()), and then reset that
temporary value.

A more general way would be to have the ability to extend
BuildConfiguration::buildProject() in a way that additional data can be
passed to the BuildSteps.

Task-Nr: QTCREATOR-5
Task-Nr: QTCREATORBUG-44

Actually that's more correct. E.g. imagine building a project, and while
the qmake step runs changing the working directory. The make step would
be affected by that. With the change both the qmake and make step get
their working directory on beeing added to the queue and so don't care
if the setting is changed afterwards.

Also: re-enable 'Step over' fallback, report error for failed breakpoints

See BAUHAUS-277

Reviewed-by: Thorbjørn

height

Task-number: BAUHAUS-291

Remove they newly introduced category sortkey.

 See: BAUHAUS-288
 Fixes some indentation

Otherwise parallel builds might fail

If the qml contains an error on frist call of
DesignDocumentController::loadMaster, we did not wire up the components
to the model. If the user then fixed the qml, the Design mode widgets
were 'enabled', but didn't contain any meaningful input.

Fixed by always wiring up the components. Unfortunately this shows the
'default' model with just a Rectangle.