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>
Handle multimap and multiset. Use the "[index] key" display that's
also used for Q{Multi,}Map both for consistency and because it's
needed to distiguish otherwise identical keys.
Change-Id: Ib9e369206bce89e5e27d1f6f60ead11ca88e2dcb
Reviewed-by: hjk <hjk121@nokiamail.com>
Get rid of IFeatureProviders that are only telling the wizard factory
that a plugin was loaded.
Change-Id: Id12c669974a6ab98036f070e1adcae35b34ca376
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
Instead pop up the "Add new expression dialog". Same amount of activity
needed, but more uniform in UI and code and hopefully less confusion
about the now-gone <Edit> marker.
Change-Id: I228801dc51f6d09ea9991b98399dc9ef04aa96c8
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
This was not accessible if the hash itself was a typedef.
Also, make sure that unusual key contents don't do any harm
in the protocol by hexencoding it unconditionally.
Change-Id: I83d43768ec72f797a72b2d9c44ca91b1feaf61a7
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
Use colors from the creator settings instead.
Task-number: QTCREATORBUG-12420
Change-Id: I477d16420a6e5d99551bb132da71ab5b28a3ff78
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
