GitLab

Reviewed-by: Thomas Hartmann
Task-number: QTCREATORBUG-4459

Reviewed-by: Marco Bubke

Reviewed-by: Marco Bubke

The Cleanlooks style is broken on the Mac atm.

Task-number: QTCREATORBUG-4296
Reviewed-by: Kai Koehne

Reviewed-by: Thomas Hartmann

Reviewed-by: Marco Bubke

Task-number: QTCREATORBUG-4317
Reviewed-by: Thomas Hartmann

Reviewed-by: Marco Bubke

Do not add QtQuick 1.0 import if we already have a QtQuick 1.1
import.

Reviewed-by: Kai Koehne

The fill button should only be checked
if all 4 anchors are set and the margins are 0.

Reviewed-by: Kai Koehne

Searching through "children" is not enough since
some items have default properties like "flickableChildren".
So we mimic instanceChildren here by taking all subnodes and
comparing the instanceParent.

Reviewed-by: Kai Koehne

To handle defaultProperties correctly in the text buffer for
copy n paste we have to forward the meta system.
Since the text buffer is not a qml document in Qt Creator
with all the infrastructure attached the meta system is
incomplete.
So we forward in these cases the meta system of the actual document.

Model::create() now gets an additional paramater where we can specify another
model for proxying the meta system.

Reviewed-by: Kai Koehne

The stack trace from 4282 indicates that in fact currentState is invalid.
We should check for this.

Reviewed-by: Kai Koehne
Task-number: QTCREATORBUG-4282

The problem was that the transaction was commited outside of the try {}
catch {} block (RAII)

1. I extended to the try block arround the fxObjectNode.setVariantProperty()
to avoid similar bugs
2. I force a commit of the transaction before leaving the try block

result:
If anything is wrong with the entered expression an exception is thrown
(like before) but now is is catched and we show a messagebox.

Reviewed-by: Kai Koehne
Task-number: QTCREATORBUG-4312

Duplicate ids for not handled 100% correctly in the property editor
and in the navigator.

Reviewed-by: Kai Koehne

Since the buffer for copy and paste has no proper
representation in the project managment QmlJs::Check cannot
handle components. For now we just turn of Check for this case, since
we check the final document anyway.

Reviewed-by: Kai Koehne

Avoid recursion if item is not movable.

Reviewed-by: Kai Koehne
Task-Nr: http://bugreports.qt.nokia.com/browse/QTCREATORBUG-4284

We have to Guard events. The Formeditor has to be fully initialized.

Task-Nr: QTCREATORBUG-4225

The combobox showing all available files did not work.

In the stateseditor we have to use propertiesRemoved instead of
propertiesAboutToBeRemoved when reseting the model. Otherwise
the change we want to react to has not happened, yet.
Some sanity checking in the property editor.

In the DesignDocumentController we slightly change the order.
The textMoifider is activated (again) before we set back the old
state.
Note: We do check for isValid() since the rewriter might delete the state.


Reviewed-by: Kai Koehne
Task-number: QTCREATORBUG-4199

Make sure that the transaction doesn't last across models.

Reviewed-by: Thomas Hartmann
Task-number: QTCREATORBUG-4136

This fixes a rare crash.

Reviewed-by: Kai Koehne

Because of overriding the double click id editing was not possible
anymore.
ChangeToComponent is still possible in the form editor.

Properties starting __ with are private api by convention.

Reviewed-by: Kai Koehne

To be safe to change to the base state (and back).

Reviewed-by: Kai Koehne

Lock setting of properties during notification.

Adding a button that allows reseting the view.

Setting a minimum size.

Task-number: QTCREATORBUG-4093

By double clicking on views the user can enter the
component (delegate).

they are a bit misleading (and embarrassing ...)

Better safe then sorry.

Task-number: QTCREATORBUG-3733

The properties x and y get removed when putting an item
into an positioner.

The user should be able to drop an item everywhere, also outside
the root item. The item is created in the scene when the animation is over.
Also the animation is shorter now.

Some items are not movable, but the user should still be able
to select them in the form editor.

Best example are items inside a positioner.