GitLab

Change-Id: Id353ab140a46e06ffc3abf667ab3b234e749e17c
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>

Getting the #include directives ready for Qt5. This includes the
new-project wizards.

Change-Id: Ia9261f1e8faec06b9285b694d2b7e9a095978d2b
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>

Change-Id: I2b72b34c0cfeafc8bdbaf49b83ff723544f2b6e2
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

Change-Id: If18afb5d4665924e7d9250dccbc60a65e6daa75e
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>

If a super class has a specifics pane use it and only autogenerate
missing properties.

In ItemPane.qml make sure the autogenerated properties come first.
Fix the template generation. If not code for any property is generated
the template is empty.

Change-Id: Ia93c55cd9f428a5ebea12d0e807a7e9ab185f0bd
Reviewed-by: Joerg Bornemann <joerg.bornemann@nokia.com>

Since we changed the slection behaivour after drag and drop
this makes the designer more responsive.

Change-Id: I21c14a126ff0b63151002ac51e841a624b43e879
Reviewed-on: http://codereview.qt.nokia.com/2033

Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>

Change-Id: I0abb528c124355808502848d5db3ec01dc3d6636
Reviewed-on: http://codereview.qt.nokia.com/1748

Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>

stateChanged() was never called.

cleanup:
I removed stateChanged() and use actualStateChanged()

Change-Id: I11a73b21dca5083147223f6e4f23da4c7305263c
Reviewed-on: http://codereview.qt.nokia.com/1677

Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Marco Bubke <marco.bubke@nokia.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>

The information change notifier provided no hint which infotmation changed.
So the property editor has updated the anchors for all information changes.
Now there is a hint and the update is only happen for a anchor change.

Change-Id: I3b6d7546f43bce4c08757662e7af32604a8db56f
Reviewed-on: http://codereview.qt.nokia.com/811

Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>

QmlPuppet only supported GraphicsView. There is now Qml2Puppet which is
supporting the new Qt Scene Graph.

Change-Id: Ia0a06639cf6852192e84f7bfc2bea60532890b08
Reviewed-on: http://codereview.qt.nokia.com/433

Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>

This class is not needed anymore and is just confusing.

Change-Id: I6ee3d4090b13d2682ff2f7b3d82ebfe1410a1344
Reviewed-on: http://codereview.qt.nokia.com/37

Reviewed-by: Kai Koehne <kai.koehne@nokia.com>

Change-Id: I8b73d583be1ee7183f4074bce49d5390e38631a2

When entering the design mode the property editor is reset.
This reduces complexity since the property editor is reset instead of
having to react to all the possible changes from text.

The same is done for the NodeInstanceView

lots of use of Utils::FileSaver and Utils::FileReader

Task-number: QTCREATORBUG-1619

Setting an empty expression on a value not defined in the model
crashed.

Task-number: QTCREATORBUG-4312

Reviewed-by: Marco Bubke

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

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

Properties starting __ with are private api by convention.

Reviewed-by: Kai Koehne

Lock setting of properties during notification.

Better safe then sorry.

Ancors work in the property editor, again.

TaskNumber: QTCREATORBUG-3958

Ancors work in the property editor, again.

TaskNumber: QTCREATORBUG-3958

Using '/' was legacy and is just confusing.
The code is way more consistent now with QmlJS and does not require
conversions.

Qt 4.7 imports are converted to QtQuick 1.0 imports.

Done-with: Marco Bubke

Reviewed-by: hjk

This was called too often.

Instead of duplicating the code from QmlEditorWigets we now subclass
and expose the gradient editing to qml.
The adaptor class is called GradientLineQmlAdaptor.

The QApplication::processEvents(); slowed it down.
Rectangle and Text is enough.

Handle different packages