Remove usage of the Q_EXPORT_PLUGIN macros, which do not exist in Qt 5.
Change-Id: I678c3cf10b9c5d5c1b9f252b0ecd1c97dc810a47
Reviewed-by: hjk <hjk121@nokiamail.com>
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
The LineEdit in the ColorEditor is not binded to a backendvalue
and we react manually to isAccepted (writeValueManually is set to true).
Because of this (and the famous focus bugs), we do not set the color,
if the selection is changed or the user enters edit mode without
pressing enter.
This patch adds the signal onCommitData to LineEdit and we react to
the signal. Because the the change of the backendvalue is delayed by
a timer we set the color immediately on the backend if we are not in gradient
editing mode.
Task-number: QTCREATORBUG-12841
Change-Id: Ic98640398c2c46b5e529780b4a9638c90760063f
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
There is no easy way to convert an enum (e.g. Qt.Vertical) to the
integer value without the meta object/QMetaEnum.
For this reason we evluate the enum as an expression
if the target property is int.
Without this patch enums do not work at all for properties defined as int.
Change-Id: I9363a84eef1bf4a3ed2c40b35f7439e249e9bd98
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
<QWidget> for QWidget, <QDataStream> for QDataStream and <QMetaObject>
for Q_GADGET (technically, qobjectdefs.h)
Change-Id: Ia7e8b12ff4c67827bb7782a0337714e330de1db1
Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
Reviewed-by: hjk <hjk121@nokiamail.com>
Since the problem is close platform link to the parent directory.
Change-Id: I6e5128e9d00ed576ce048d1d48db61e6f758a979
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
The window mockup now contains some support for the toolbar of
ApplicationWindow. The status bar is always invisble and just
a place holder.
I reduced the import for QtQuick 2 to support Qt 5.1.
Change-Id: Ic2241bf3fdd0d2967f988add06075a9e145a1cbc
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
I do not see any reason to set an expression that contains a
code block.
Change-Id: I74960a6bac741db46d86e33299e8b1669e781e65
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
There is no real reason to ever instantiate those.
Change-Id: I1bb86b5f5794f10bf2cad124499df6ee8add6909
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
If we cannot read the index we set the index to 0.
Change-Id: Id990ca1640f9314931af9249c798c8b51ea5c0bb
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
Came from two deletions at the same time QCache::remove and
delete on sharedMemory.QmlDesigner:
Change-Id: I6a29cf160c8e81ecd955cf36999edc639fbbb63f
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
To be sure that the shared memories are removed at process exit.
And fix that createSharedMemory reuse possible already existing shared
memories now. ("take" -> "[]")
Change-Id: Idcc99ba42b862b862d5403ecf3b781a27fdf757f
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
OS X is only supporting a maximum of 31 letters for shared memory names.
Change-Id: I61351228decaa3fa7ec19a6035620ab932cf5386
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
We use left padding instead of a prefix.
Task-number: QTCREATORBUG-12781
Change-Id: I0c89e3592ad0ca9c498d33930ef2742ec970f8bb
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
QSharedMemory is using SVR4 shared memory for unix which is limited to
4 MB globally which is really hurting the performance for the designer.
POSIX shared memory is lifting some of this constraints but still has
some bugs on Max OS but generally works better.
Change-Id: I74c1ffd56495f408cd9340cd159190a1175a4086
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
This is a property of ListView and GridView.
Task-number: QTCREATORBUG-12507
Change-Id: Ie3f6db2f90bc8b67bcc208c709b87717f653525d
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
I set corner to an empty item, because otherwise it looks weird if both
scrollbars are visible.
Change-Id: I149e2ff58f9e9f71b2bb9f435fd64388cbf5529c
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
Since property change signals can be emitted in any order we have to rely
on selection changed signals to guarantee a valid state.
I use the isInValidState which is only true after all properties have been
setup correctly after a selection change for this.
I added the signal selectionChanged for this.
Task-number: QTCREATORBUG-12642
Task-number: QTCREATORBUG-12506
Change-Id: Idf3bbe8236ece541ca267efb1bd68e0737c99716
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
I gave writeValueManually a proper name and added a missing check.
Task-number: QTCREATORBUG-12642
Change-Id: I67b0d7754647c29ef378d6f12f023c8a4e728cd2
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
