- 18 Feb, 2014 6 commits
-
-
Ulf Hermann authored
Change-Id: I3a85322cc583de37f1cc4eb256e3382a92c5c179 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Change-Id: I32ab2e354d3e45653e8dcb2cf8b0195d199786a6 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Without this you get lines like this on the console: SOFT ASSERT: "m_state == Done || m_state == Empty" in file [...]/qmlprofilermodelmanager.cpp, line 62 Change-Id: Ia3fb98cd5e9fb683e3265d0fd3ed1ca99784270d Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
We don't want to emit a signal for each event being added. That's expensive and doesn't serve any purpose. We also don't have to save the availability of data in QML as it isn't used anywhere. Change-Id: I32db06a1955a7cfd6b569f50b81bf5278333b622 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Allow adding a weight to certain tasks so that the movement of the bar gets smoother and update the progress from more places. Change-Id: Ifb8331dc77116cc0464b3970cd6344fbbeacec41 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
The model manager should only set its state to 'Done' if all models are actually done. When that is the case it can safely emit dataAvailable, too, freeing us of the need to apply a heuristic to the progress percentage. In order to have a unified interface to the completion of model processing an abstract base class for QML and V8 models is introduced. Task-number: QTCREATORBUG-11466 Change-Id: Id89c7ef5e24004baab7f37ee5486b69e7611aee0 Reviewed-by:
Christian Stenger <christian.stenger@digia.com> Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 14 Feb, 2014 1 commit
-
-
Ulf Hermann authored
Binding loop markers aren't ordered in any particular way so we cannot stop drawing them when we find an invisible one. Change-Id: I16dcc96c15febc5cfe0203e23c1ca657714a2c25 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 12 Feb, 2014 1 commit
-
-
Orgad Shaneh authored
Done using the following ruby script: Dir.glob('**/*.h').each { |file| if File.file?(file) s = File.read(file) t = s.gsub(/^namespace .+ \{\n\s*class .*;\n\s*\}.*$/) { |m| m.gsub(/\n\s*/, ' ').gsub(/\s*\/\/.*$/, '') } if t != s puts file File.open(file, 'w').write(t) end end } Change-Id: Iffcb966e90eb8e1a625eccd5dd0b94f000ae368e Reviewed-by:
hjk <hjk121@nokiamail.com>
-
- 11 Feb, 2014 1 commit
-
-
Tobias Hunger authored
... based on output from dependencyinfo.py script Change-Id: I9532f6d259f15c16b62fae0ca18f8a8cad95bd11 Reviewed-by:
Christian Kandeler <christian.kandeler@digia.com> Reviewed-by:
Christian Stenger <christian.stenger@digia.com> Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com>
-
- 10 Feb, 2014 2 commits
-
-
Ulf Hermann authored
Change-Id: I781b95bdd9d6bfa12ec8f40f4197119ba51e194a Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Change-Id: I11d22ce1423384f879e30ff9573f4d7d799535b1 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 28 Jan, 2014 1 commit
-
-
Fawzi Mohamed authored
* better support qbs and similar non QtQuick qml languages * begin to clean and migrate things from ModelManager to ModelManagerInterface Change-Id: Ifa39dc1e4c568e9e21307f4913dcb5989e80420f Reviewed-by:
Thomas Hartmann <Thomas.Hartmann@digia.com>
-
- 14 Jan, 2014 3 commits
-
-
Ulf Hermann authored
Anchors are supposed to reduce graphical glitches such as the gradient borders getting detached from the edges of the timeline while resizing. I'm not sure if it's actually better like this, but the code certainly looks nicer. Change-Id: I9eb6a6a50780ce642ad7cb551d2895a80b00690e Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Change-Id: Iaff416c1af61e20e47309b7ec34bf4ab0d3f4267 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
This is a temporary fix to work around the fact that the profiler's loading indicator won't show on top of the timeline view. It's not particularly beautiful but at least the UI doesn't just "hang" anymore. A final solution has to be provided in qtdeclarative by allowing widgets to be placed on top of QML scenes. In principle it's also possible to change the loading indicators to be actual windows and by doing that have them stay on top, but the result would be very messy. Change-Id: Ic774b0792786d7d278da5ba0beda4531f0dba77d Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 13 Jan, 2014 2 commits
-
-
Ulf Hermann authored
Hiding a category in the timeline view is highly confusing. Previously the "Painting" category would only be visible if either the model is empty or at least one painting event was available. Like this it's always there. In the obscure case of a mixed Qt4/Qt5 application you can get two "Painting" categories now. Change-Id: I54db106ed868b7e5d46d0e0ac22b46c0df8be862 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Previously the animation paint events could overlap if the framerate estimates were off by more than 1 event. Furthermore the duration could be negative or 0, with a potential crash in the latter case. Also it's a bad idea to change the server-provided framerate to suit our estimated durations. Change-Id: I14da0855d7248a6ef32509572caa439ebb2d430e Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 09 Jan, 2014 1 commit
-
-
Robert Loehning authored
Change-Id: I6e25ba25aa2898b5382dae7f3751deebb6072efa Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 08 Jan, 2014 1 commit
-
-
Robert Loehning authored
Change-Id: Ib5423fdd064e4546f848c0b640b0ed0514c26d3a Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@digia.com> Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 02 Jan, 2014 6 commits
-
-
Ulf Hermann authored
Loading data on ProcessingData would lead to incomplete information about source code locations. Rebuilding the whole model on any kind of changed() signal is wasteful. Task-number: QTCREATORBUG-11100 Change-Id: I9f8d718bff6149ca2dc2d0482c11d66d940af15d Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Previously, the QmlProfilerSimpleModel would report a count of 1/1 when empty while all others report 0/1. This leads to the UI waiting forever for the "missing" data. Task-number: QTCREATORBUG-11095 Change-Id: I165278caa5a2bece362bf869608d501d7f553c91 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
By returning early from the method painting the binding loop markers painter states could be left on the stack, triggering error messages later. Change-Id: I0b9c336e44a28feec96c506d0e3d0da291054bbd Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
It's a good idea to start a new path for each of them. They're quite unrelated after all ... Task-number: QTCREATORBUG-11099 Change-Id: Id47e482b948a0827018c71ddc8d13e2e69829bc4 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Task-number: QTCREATORBUG-11094 Change-Id: I9e3ef29b6f14d44e15df16ec051b33ea9393968b Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Having a mouse area larger than the item to be dragged certainly creates funny effects, but isn't really useful... Change-Id: I98efb7a6145a09edfdbc090b34bb306383b302cd Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 16 Dec, 2013 1 commit
-
-
Friedemann Kleint authored
Change-Id: I704ba93d01ffababb405bc801f07a845631930cc Reviewed-by:
Daniel Teske <daniel.teske@digia.com>
-
- 13 Dec, 2013 1 commit
-
-
Ulf Hermann authored
Without this all the data is processed another time in all timeline models when the second signal is emitted. This is quite wasteful. Task-number: QTCREATORBUG-10950 Change-Id: Iac1315689e0900abb48efc1cf6390ec559a1897c Reviewed-by:
Kai Koehne <kai.koehne@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 12 Dec, 2013 2 commits
-
-
Kai Koehne authored
React to a second changed() signal from the simple model that is emitted after the binding text has been retrieved from the local files. This will rebuild the whole model effectively twice ... ideally we'd just update the text, but it shouldn't be a performance problem, either. Change-Id: I71a47f0faddd3938711e2e190f1e9c961be343e4 Reviewed-by:
Ulf Hermann <ulf.hermann@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
Ulf Hermann authored
Change-Id: Ib511897b5a314d36e906d7c52a09a88c281925fc Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 11 Dec, 2013 5 commits
-
-
Ulf Hermann authored
Change-Id: I259d2e49c247fc512b0c5ced2d3f3a5a68312c4b Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
By using the QML Grid element the windows' widths can be made dynamic, preventing text overflow while still retaining the two-column-layout. Change-Id: I8b70027126aef5f9e2c4176245caf1b472df4040 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
This allows us to steer the timeline models in a more fine grained way and avoid duplicate processing of the same data. We don't need to rebuild everything on stateChanged of the model manager then. Task-number: QTCREATORBUG-10950 Change-Id: I2aa9a96a33c602f062fc3b644ac06280ba7cd45a Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
The same code was repeated all over the place. Change-Id: I70a8caa46c91a7b55fd7eecac32cdc53b5d94cfb Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Those functions aren't called from anywhere. Wheel zooming has been removed a long time ago and centering is handled in a different way. Change-Id: Ib55fdfdd3cf794563eaa50ff9b5f1a1dfe94a17a Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 09 Dec, 2013 1 commit
-
-
Ulf Hermann authored
In order to unify the uses of range data and the calculation of first and last ranges in visible areas we need a template class to provide the respective algorithms. Change-Id: I1c2e9c9fa9ae048262026236c4ff39017ab7913f Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 03 Dec, 2013 3 commits
-
-
Ulf Hermann authored
The canvas integrated in QtQuick does the same thing. We can remove a lot of code like this. Change-Id: I6425ae4e1b542107defd9d76fa5755712a0f8613 Reviewed-by:
Ulf Hermann <ulf.hermann@digia.com> Reviewed-by:
Christian Stenger <christian.stenger@digia.com> Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
As the contentWidth depends on both the width of the flickable and the currently selected time range it should be updated if either of them change. Otherwise we can miss changes and show stale data. Change-Id: Iab9e17eef3490531175a2374fb3da0e0071f3bd1 Reviewed-by:
Christian Stenger <christian.stenger@digia.com> Reviewed-by:
Kai Koehne <kai.koehne@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
Ulf Hermann authored
As it's hard to pass arguments for signals from non-QML-mapped objects to QML objects handle the signal in C++ instead and just directly set the properties. Task-number: QTCREATORBUG-10943 Change-Id: I039f6938db3d7e64ca1a4bcff2f0f6aa79c65219 Reviewed-by:
Kai Koehne <kai.koehne@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 02 Dec, 2013 1 commit
-
-
Ulf Hermann authored
When selecting ranges in the timeline the selector would sometimes hang or behave weirdly when moving back. This was due to incorrect logic in the selection bounds calculation and because the vertical flicking would steal mouse events. Change-Id: I14074463422d1d9a0aa8ecd1f88847e7330c9b6b Reviewed-by:
Kai Koehne <kai.koehne@digia.com> Reviewed-by:
Ulf Hermann <ulf.hermann@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 29 Nov, 2013 1 commit
-
-
Tobias Hunger authored
Change-Id: Ia67d98855548c4d2c80ad76ff633a2399e30ad9c Reviewed-by:
Ulf Hermann <ulf.hermann@digia.com> Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-