- Apr 26, 2011
-
-
Christian Kamm authored
-
- Apr 21, 2011
-
-
Christian Kamm authored
Fixes the problem 5426c3ac and 7b25f438 worked around. Reviewed-by: Erik Verbruggen
-
- Apr 13, 2011
-
-
hjk authored
-
- Apr 12, 2011
-
-
Kai Koehne authored
Don't underline the import if a qmldump fails, but the typeinfo is available via a .qmltypes file. That should allow users to 'fix' qmldump issues by shipping a .qmltypes file. Reviewed-by: Erik Verbruggen
-
- Mar 11, 2011
-
-
Christian Kamm authored
-
- Mar 10, 2011
-
-
Christian Kamm authored
Reviewed-by: Erik Verbruggen
-
- Feb 21, 2011
-
-
Christian Kamm authored
The problem was that several lookup calls suddenly failed because the actual QML types were no longer in the default scope chain. However, the QML documentation says the type names are in the scope. Also, 'MyComponent.' in a JS-expression context only showed the attached properties of MyComponent and missed the enums. With this change completion now may offers too many options, but that's better than missing some. This reverts parts of 490f2797 Reviewed-by: Leandro Melo
-
- Feb 10, 2011
-
-
Christian Kamm authored
-
Christian Kamm authored
Having a duplicate prototype chain - once in FakeMetaObjects and once in QmlObjectValues was unnecessary. Now FMOs don't contain references which may allow other simplifications.
-
Christian Kamm authored
That means createComponent etc. will now be completed.
-
- Feb 09, 2011
-
-
Christian Kamm authored
-
Christian Kamm authored
-
Christian Kamm authored
In preparation of relocatable plugin types.
-
Christian Kamm authored
-
Christian Kamm authored
Task-number: QTCREATORBUG-3048
-
- Jan 12, 2011
- Jan 10, 2011
-
-
Christian Kamm authored
There was trouble when a plugin qmlRegisterType'd something like 'Item' into the global default module. Reviewed-by: Roberto Raggi
-
- Jan 06, 2011
-
-
Christian Kamm authored
By moving the offending code into a background thread. Reviewed-by: Erik Verbruggen
-
Christian Kamm authored
Previously they were leaked when a qmldump or the C++ exported QML type list updated. Just deleting the previous FakeMetaObjects is not an option, as they might still be used in a QmlObjectValue owned by an Engine. Reviewed-by: Erik Verbruggen
-
- Jan 04, 2011
-
-
Christian Kamm authored
Reviewed-by: Erik Verbruggen
-
Christian Kamm authored
-
- Dec 17, 2010
-
-
con authored
-
- Dec 01, 2010
-
-
Thomas Hartmann authored
Those are needed for the Visual Editor Reviewed-by: Christian Kamm
-
Thomas Hartmann authored
We should differentiate between int and real Reviewed-by: Christian Kamm
-
- Nov 25, 2010
-
-
Christian Kamm authored
* Bind::usesQmlPrototype is now significantly more performant * type environments are no longer hashed by filename, but rather by Document * * duplicate scope builds are avoided Task-number: QTCREATORBUG-2835 Reviewed-by: Erik Verbruggen
-
- Nov 17, 2010
-
-
Christian Kamm authored
-
- Nov 16, 2010
-
-
Christian Kamm authored
Reviewed-by: Erik Verbruggen
-
- Nov 15, 2010
-
-
Christian Kamm authored
-
- Nov 12, 2010
-
-
Christian Kamm authored
This will allow distinguishing mere strings from urls and allow different completion. Reviewed-by: Erik Verbruggen
-
- Nov 11, 2010
-
-
Thomas Hartmann authored
We have to follow the prototype chain Reviewed-by: Christian Kamm
-
Thomas Hartmann authored
Reviewed-by: Christian Kamm
-
Christian Kamm authored
Added hasLocalProperty() hasProperty() keysForEnum() Reviewed-by: Christian Kamm
-
Thomas Hartmann authored
This allows to distinguish between int an real numbers Reviewed-by: Christian Kamm
-
Thomas Hartmann authored
Reviewed-by: Christian Kamm
-
Thomas Hartmann authored
Done-with: Christian Kamm
-
- Oct 27, 2010
-
-
Christian Kamm authored
The detection of whether a type or one of its children is exported was broken when we fixed the type information for the QtQuick module. Reviewed-by: Erik Verbruggen
-
- Oct 19, 2010
-
-
Christian Kamm authored
Reviewed-by: Erik Verbruggen
-
- Oct 08, 2010
-
-
Christian Kamm authored
This is the name that other components will refer to it by. For instance, MouseArea has a 'drag' property with type 'QDeclarativeDrag', since QDeclarativeDrag was only exported as Qt.Drag and QtQuick.Drag, the type lookup didn't manage to resolve the name. (cherry picked from commit b53ba612)
-
- Oct 07, 2010
-
-
Christian Kamm authored
This is the name that other components will refer to it by. For instance, MouseArea has a 'drag' property with type 'QDeclarativeDrag', since QDeclarativeDrag was only exported as Qt.Drag and QtQuick.Drag, the type lookup didn't manage to resolve the name.
-