- Feb 10, 2011
-
-
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
-
hjk authored
-
hjk authored
-
Leena Miettinen authored
Removed duplicate info. Reviewed-by: hjk
-
Pawel Polanski authored
-
Thiago Macieira authored
-
Marco Bubke authored
-
Christian Kandeler authored
Task-number: QTCREATORBUG-3782
-
Friedemann Kleint authored
-
Christian Kandeler authored
Task-number: QTCREATORBUG-3771
-
Christian Kandeler authored
Task-number: QTCREATORBUG-3229 Reviewed-by: Alessandro Portale
-
mae authored
Done-with: Leandro Melo
-
Oswald Buddenhagen authored
if the exact evalution fails (possibly because of a parser error), then still use the cumulative evaluation to construct the project tree. only the target information won't be updated and the code model will be left in the dark. todo: the errors are dumped only to the (unnumbered) "general messages" output pane, which makes them practically invisible. Task-number: QTCREATORBUG-3093
-
Oswald Buddenhagen authored
instead of erroring out the parse, only error out the evaluation in exact mode. that way we can do cumulative evaluation even on broken files. Task-number: QTCREATORBUG-3093
-
Oswald Buddenhagen authored
it would collect global values instead.
-
Oswald Buddenhagen authored
special-casing it makes no sense, as all other values from the project would be mismatched and thus worthless for code validation anyway.
-
Oswald Buddenhagen authored
the node updater would check if the cumulative and exact evalutor returned the same project type and would discard the cumulative one if they didn't. this was pointless, as a) it would practically never happen and b) it would be without much consequence anyway.
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
... otherwise oldValues equals newValues. the signal is currently not connected anyway, but whatever.
-
Oswald Buddenhagen authored
this kinda worked because int(ReturnTrue) == int(true), but there are more possible return values than that.
-
Oswald Buddenhagen authored
-
Christiaan Janssen authored
Reviewed-by: Kai Koehne
-
hjk authored
Old logic was too fragile to maintain. Now it's PointMixed -> PointPlain -> RangeMixed -> RangePlain.
-
hjk authored
-
Christian Kamm authored
That means createComponent etc. will now be completed.
-
Kai Koehne authored
-
Kai Koehne authored
-
- Feb 09, 2011
-
-
Alessandro Portale authored
Now using an explicit Mode (generated, imported) instead of empty or set filename convention. Just like in Html5App.
-
Thorbjørn Lindeijer authored
-
Thorbjørn Lindeijer authored
Some things forgotten as part of commit f9e65028 since these files are not compiled together with Qt Creator. Fixes compile of QML Observer and QMLJSDEBUGGER-enabled QtQuick Applications.
-
Thorbjørn Lindeijer authored
AbstractFormEditorTool -> AbstractLiveEditTool LayerItem -> LiveLayerItem SelectionIndicator -> LiveSelectionIndicator SelectionRectangle -> LiveSelectionRectangle SelectionTool -> LiveSelectionTool SingleSelectionManipulator -> LiveSingleSelectionManipulator RubberBandSelectionManipulator -> LiveRubberBandSelectionManipulator
-
Leandro Melo authored
Task-number: QTCREATORBUG-2968 Reviewed-by: Alessandro Portale
-
Alessandro Portale authored
Reviewed-By: Christian Kandeler
-
Marco Bubke authored
-
Marco Bubke authored
All type information should be now available.
-
Marco Bubke authored
-
Alessandro Portale authored
-
Alessandro Portale authored
-
Alessandro Portale authored
-