The TextEditorSettings class already provides the appropriate signal.

Reviewed-by: kh

the sub-strings "escaped" from the evaluator through the accessor, so
things did go boom, after all.

Reviewed-by: thorbjorn

- allow for more verbose description
- allow to fit all catagories and subcategories in
- bring more clear separation between projects and files
- expense: one more click

Reviewed-by: jbache

This is a preperation towards being able to present the dialog
in a different layout, with slightly improved usability.

Reviewed-by: jbache

as requested by popular vote

Task-number: QTCREATORBUG-1116

There was a subtle bug in propertyReseting() that caused a gradient
property of a Rectangle not to be removed, if the gradient was deleted.
Deleting the gradient triggered a reparenting operation in the
nodeinstances where the resetProperty() of the oldParent was not
executed properly.

This caused a dangling pointer in QDeclarativeRectangle.

Reviewed-by: Marco Bubke

Task-number: QTCREATOR-207
Reviewed-by: ck

Reviewed-by: Erik Verbruggen

Also, the hint on milliseconds was wrong. The unit is seconds.
As requested by Friedemann.

So now the "Applciation Output" can distinguish between these four, and
handle them appropriately.

By introducing the OutputFormatter, RunControls can influence the formatting
depening on the application started. A nice (and intended) side-effect is that
the QML runtime specific formatting will not interfere anymore with anything
else.

This adds gradient editing and is a solution for BAUHAUS-445

See: BAUHAUS-590

 ... if it is part of the drive letter only.

Reviewed-by: kh1

Reviewed-by: kh1