* Report what kind of build we have in the tooltip
 * Create only debug/release configuration for debug/release
   configured directories
 * Create debug and release configuraions for debug_and_release
   configured directories
 * Add debug_and_release to options in QMakeStep UI
 * Do not add CONFIG+=debug/release to CONFIG+=debug_and_release builds

Reviewed-by: Tobias Hunger

Otherwise, if the project file does not already end in a newline,
we'd introduce syntax errors.

Remove unneeded methods from API.

Reviewed-by: Tobias Hunger

Reviewed-by: ck

(Else, we do do not have enough time to start the observer)

Dumping property is too slow and introduces noticable leaks

In order to work, this optimisation needs f7a501515fcf1dafecb88
from Qt.  (else it will not get optimized)

Do the same as in CppOutline

Application logic implemented. The Wizard Ui does not expose
this feature, yet.

QmlStandaloneApp::path() used to combine the separate enums.
But most of the combinations would not make sense. Now, path()
uses the combined enum and maintainability won this time.

This commit repeats 34f241c0 . Looks like that didn't survive the merge.

Task-number: QTBUG-12057

Filtering MouseButtonPress and MouseButtonRelease
makes no sense and results in bad behaivour when
dragging the QuickToolBar.

We have to check for  m_oldCursorPosition != -1
to avoid calling apply() in the case of a TextMarker
update. Otherwise the QuickToolBar misbehaves.

I also removed the comment.

This was just plain wrong.
A negative offset makes no sense in any
case.

This resolves several usability bugs.

The painting was visible slow before.
Avoiding QPainter and setting pixels
directly leads to serious speedup.

If font.bold/font.italic etc. are set to anything,
but a literal boolean, the button gets disabled, now.
This prevents the user from accidentally overiding
bindinds.

The textmarker is now updated when the document
gets updated and the textmarker is shown again,
if the user closes the QuickToolBar.