- 08 May, 2013 - 10 commits
-
-
Liang Qi authored
This breaks Qt Quick Controls activeFocusOnTab autotests. This reverts commit 305616a6 . Change-Id: Ided59ebe99659b23e950e8269ccaa8d7d44a4fdb Reviewed-by:
Jens Bache-Wiig <jens.bache-wiig@digia.com>
-
Thomas Hartmann authored
Change-Id: Id6e157aa191aaa4e24a9cd5c76abfe902fe43d44 Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@digia.com> Reviewed-by:
Jan Arve Sæther <jan-arve.saether@digia.com>
-
Kai Koehne authored
Since this is popping up quite regularly, add an explanation why we need qmlplugindump to be an application bundle. Change-Id: Iacf5ad0742aa9fb601c3be046f268764df062e81 Reviewed-by:
Tor Arne Vestbø <tor.arne.vestbo@digia.com> Reviewed-by:
Oswald Buddenhagen <oswald.buddenhagen@digia.com>
-
Thomas Hartmann authored
Resources was a direct mapping of the QObject children. This led to problems since the QObject children can also contain other objects from other sources like attached properties. This patch decouples resources from QObject properties and also does not call setParent() anymore. The special case for QQuickWindow in data_append does rely on the fact that QObject::setParent() is called and the inner window becomes a QObject::child of the content item. So we keep the setParent for this special case. The children property does not take QObject ownership either. QObject ownership is handled by the VME. None of the documented QML use cases should be touched by this change. This is a cleaner solution then the ad hoc fix provided by https://codereview.qt-project.org/#change,54677 I changed also the test. The list count now has to be exactly 4. Change-Id: I5c119e333ee82e888aaac1da559fd63a875d08ee Reviewed-by:
Liang Qi <liang.qi@digia.com> Reviewed-by:
Shawn Rutledge <shawn.rutledge@digia.com>
-
Oswald Buddenhagen authored
Change-Id: I34ea6a8ea5f6f2641bf5deaf2a7136e5ed51a8ba Reviewed-by:
Alan Alpert (Personal) <416365416c@gmail.com>
-
Oswald Buddenhagen authored
Task-number: QTBUG-30676 Change-Id: I5c5869ee3050e67390607f94054127bd62ab2ea4 Reviewed-by:
Andy Shaw <andy.shaw@digia.com> Reviewed-by:
Liang Qi <liang.qi@digia.com>
-
Shawn Rutledge authored
An application can implement onClosing() and set closeEvent.accepted = false to delay the closing (for example to prompt the user to save changes). Depends on change I9abed47fca02a002b78727f98d678a824854adfc in qtbase. Task-number: QTBUG-31019 Change-Id: Icfd4a03ecef3621bdbbee2e2c3157b897a9b6524 Reviewed-by:
Alan Alpert (Personal) <416365416c@gmail.com>
-
Liang Qi authored
Iterate all or not in nextPrevItemInTabFocusChain function. Change-Id: I14d40dbeda01ca470efe23886789383ff1d30c0f Reviewed-by:
Gabriel de Dietrich <gabriel.dedietrich@digia.com>
-
Jan Arve Saether authored
The snippets that qqmlxmllistmodel.cpp referred to could not be found. xmlrole.qml is only referenced from src/imports/xmllistmodel/qqmlxmllistmodel.cpp Change-Id: I95f962927097cd9d3295fbc2b376a9ab27ae6e5c Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com>
-
Alan Alpert authored
Objects were not being created correctly when the model changed after componentComplete. After correcting that the model change can lead to an intermediate count change when the old model is cleared, so a flag is set to ignore intermediate changes fom the QQmlDelegateModel when the model changes. Task-number: QTBUG-30379 Change-Id: I55519c9ee378a1b0569567137ebd378f32a6c85c Reviewed-by:
Caroline Chao <caroline.chao@digia.com> Reviewed-by:
Christopher Adams <chris.adams@jollamobile.com> Reviewed-by:
Gabriel de Dietrich <gabriel.dedietrich@digia.com>
-
- 07 May, 2013 - 5 commits
-
-
Alan Alpert authored
Registered types are stored in a global static variable, not on an engine instance. For applications managing multiple engines over their lifetime, there needs to be a way to clear the existing types so they can register new ones and avoid memory leaks. Task-Number: QTBUG-28572 Change-Id: Ic70a4dd1e29d99399b21fb42eaf10d4a52bf2adf Reviewed-by:
Christopher Adams <chris.adams@jollamobile.com>
-
Alan Alpert authored
Allows for custom file handling to a greater extent than the QNetworkAccessManager. Change-Id: Ifd3946bf33530c40ca2edeeb9f441f712e4941f6 Reviewed-by:
Matthew Vogt <matthew.vogt@qinetic.com.au>
-
Sze Howe Koh authored
Add screenshots and brief descriptions. Integrate source code into documentation. Create new group, "qtquickdemos". Change-Id: I92715b2cdd861b1ff2bdd28a640e63d2a220499e Reviewed-by:
Topi Reiniö <topi.reinio@digia.com> Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com>
-
Leonard Lee authored
Task-number: QTBUG-28711 Change-Id: Icb44359397dcd5407652ff105154124666d0306d Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com>
-
Gunnar Sletta authored
Change-Id: Iac3c8d60d531a93ce6e862dbdfdf53e49e0d2185 Reviewed-by:
Alan Alpert <aalpert@blackberry.com>
-
- 06 May, 2013 - 4 commits
-
-
Sze Howe Koh authored
Change-Id: Ib79bfbea402b86e26a503de47383522317ca906b Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com>
-
Sze Howe Koh authored
Most of the example titles have either a "Qt Quick Examples -" prefix or a "Scene Graph -" prefix. Also fixed a typo ("Scenegraph" -> "Scene Graph") Change-Id: Ibeb25d88d1888be3fb004a9ad95dc7ccbfeed7e3 Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com>
-
Christiaan Janssen authored
Change-Id: Ide71b330b13fc3816ed191bd9af84e0fce0d9587 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Sze Howe Koh authored
"qtquickexamples" is for illustrating code usage; "qtquickdemos" is for showcasing fully-functional apps. Renamed titles and screenshots to match the other demos. Also, attempt to make the descriptions sound more interesting. Change-Id: I2fb43c5d32f24159cd39564576d4ebd76b2cbeaa Reviewed-by:
Alan Alpert <aalpert@blackberry.com> Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com>
-
- 04 May, 2013 - 6 commits
-
-
Shawn Rutledge authored
Also removed the rotation animation which doesn't seem useful. (On most platforms the content will auto-rotate anyway.) Change-Id: Ia6ca1046fc2162a13be5c26cbf5d2b698ffa2367 Reviewed-by:
Richard Moe Gustavsen <richard.gustavsen@digia.com>
-
Shawn Rutledge authored
Follows the same reasoning as Iefe63cd753f9f8bb04278fd04a4d728e3deda25e in qtbase: buttons should have only the buttons which are still pressed. Change-Id: I894df43254eb1b1ce173fd7acc7190e9765beb48 Reviewed-by:
Richard Moe Gustavsen <richard.gustavsen@digia.com> Reviewed-by:
Frederik Gladhorn <frederik.gladhorn@digia.com>
-
Liang Qi authored
Task-number: QTBUG-30919 Change-Id: I474a327e057978356a4ae395d8f59a66afaf2f7f Reviewed-by:
Alan Alpert <aalpert@blackberry.com>
-
Eskil Abrahamsen Blomfeldt authored
When we're bundling Qt inside the apk, we need to know which extra files to bundle which might be dependencies of the app. In this case, qml/ which contains the imports for Qt Quick 2, and the accessible/ plugins. Change-Id: I0782a6146a4d41d895db20d912eb6877e54ef6c8 Reviewed-by:
Paul Olav Tvete <paul.tvete@digia.com>
-
Alan Alpert authored
emitCap is intended to prevent issues with multiple emission of infinite life particles, but it can currently prevent emission of any particles when particleCount() changes after a reset. Tracking particleCount() on changes would be inefficient and be more work to integrate with the correct behavior of infinite particles, so this patch delays the impact of emitCap until an infinite particle is discovered. This will lead to a subtle behavior difference of limiting infinite particle counts based on the count at the first emission, not the first reset, which could be construed as a bug fix in some situations. This seems reasonable as a futher subtle behavior change will be needed in the future to properly support varying counts of infinite particles. Task-number: QTBUG-30915 Change-Id: I4172aee1d03f00cc63ce7c9d12ace052bc41436d Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com>
-
Alan Alpert authored
In the case where a QML type had been registered with the same metaobject, you could dereference the c++ type union data when it hadn't been allocated. Change-Id: I906d68710cf88b379933eb13cf0668738f07d5f4 Reviewed-by:
Matthew Vogt <matthew.vogt@qinetic.com.au>
-
- 03 May, 2013 - 9 commits
-
-
Topi Reinio authored
This change moves 'Extending QML' qdoc file and the tutorials from examples/quick to examples/qml, which is the correct location for them. Change-Id: I24bd9dfa75baaab7bc8efe08489f09a7b65d98a6 Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com> Reviewed-by:
Sze Howe Koh <szehowe.koh@gmail.com> Reviewed-by:
Alan Alpert <aalpert@blackberry.com>
-
Michael Brasser authored
The scenegraph as a whole does not typically do GL error checking. That means GL errors occurring elsewhere could cause the etcprovider to unload textures that loaded correctly. Change-Id: Ic8e0caa62dab50b391e226cf0a493bc7e357dc46 Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com>
-
Albert Astals Cid authored
It can happen that when the QQmlDelegateModel goes away some of the QQmlDelegateModelItem from d->m_cache are still incubating, this means that isReferenced() will return true and we will not delete them. This also means that when these QQDMIncubationTask finish they may end up calling QQDMIncubationTask::statusChanged which will try to access the delegate model that is already gone. This commit makes sure we set vdm to 0 in these orphaned QQDMIncubationTask so in QQDMIncubationTask::statusChanged we know no one cares about us anymore and don't reference the already gone delegate model Task-number: QTBUG-30928 Change-Id: Ief6176cec151d861dad09ca2498ca27e17ee6385 Reviewed-by:
Andrew den Exter <andrew.den.exter@qinetic.com.au>
-
Samuel Rødal authored
Fixed blur being too faint by fixing the weight to correctly match the amount of pixels being sampled based on the blur radius, and by not multiplying and flooring to int inside the sampling loop which leads to excessive rounding down errors. The "half" value in the previous implementation was also wrong due to using integer division instead of floating point division, which caused the blur being slightly offset down and to the right. By not calling scanLine() and constScanline() repeatedly and by only applying the weight once in the single-weight case we can also gain a slight performance improvement. Also, make sure blur radii below 2 don't get floored to 0. Change-Id: Ibe15d0f51c919594b168923485c051d21f8d7822 Reviewed-by:
Mitch Curtis <mitch.curtis@digia.com> Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com>
-
Samuel Rødal authored
If the item being rendered didn't have a bounding rect starting in the origin the shadow path would be get an additional offset equal to the distance of the item from the origin. Also, the stroke's shadow did not take the pen width into account, causing clipping artifacts. Combine all the common shadow generating code into a single function, and avoid rendering into an intermediate image that is then blitted into a larger image. Task-number: QTBUG-30914 Change-Id: I16c7c15897ab8e2d46f37da835f75f97fe680863 Reviewed-by:
Mitch Curtis <mitch.curtis@digia.com> Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com>
-
Frederik Gladhorn authored
The path already has the transform, no need to apply it a second time manually. Task-number: QTBUG-30501 Change-Id: Iedcb2e2f85a1f9eeac8e6264e00536c43bf16ddb Reviewed-by:
Samuel Rødal <samuel.rodal@digia.com>
-
Morten Johan Sørvig authored
Enabling touch events on a window causes scroll event lag so we want to avoid avoid it as far as possible. Enable/disable on scene changes, similar to what we do for WA_AcceptTouchEvents for widgets. Task-number: QTBUG-28483 Change-Id: I2e5b5e2b093cccfc5253f7228f5ec0c588c60371 Reviewed-by:
Shawn Rutledge <shawn.rutledge@digia.com> Reviewed-by:
Gabriel de Dietrich <gabriel.dedietrich@digia.com>
-
Shawn Rutledge authored
Enabling touch events on a window causes scroll event lag so we want to avoid avoid it as far as possible. Enable/disable on scene changes, similar to what we do with WA_AcceptTouchEvents for widgets, and in change I2e5b5e2b093cccfc5253f7228f5ec0c588c60371 for MultiPointTouchArea. Change-Id: I8cd8d172ffd93cfc4ec115917cc8662202f3b069 Reviewed-by:
Gabriel de Dietrich <gabriel.dedietrich@digia.com>
-
Alan Alpert authored
When hoverEnabled is unset the item remains in a hovered state until the mouse leaves. In this circumstance, the item could be destroyed without cleaning up the reference in the hovered items list. To catch this and similar circumstances, the item is removed from the list when destroyed, regardless of hoverEnabled status. Task-number: QTBUG-30962 Change-Id: I982ab8c9e1077fecc885fd166d70bbbbbe8fc179 Reviewed-by:
Shawn Rutledge <shawn.rutledge@digia.com> Reviewed-by:
Liang Qi <liang.qi@digia.com>
-
- 01 May, 2013 - 2 commits
-
-
Alan Alpert authored
QJSEngine doesn't call collectGarbage upon deletion, because this operation can be expensive and in most cases the JS engine is deleted during application shutdown, when the memory can be deallocated cheaper. This can lead to an apparent memory leak if multiple engines are created and destroyed in the same process. Documenting how to avoid this. Change-Id: Ie02cb8bedc8821e0bb04dfa52a5a2d65b4b085a3 Reviewed-by:
Christopher Adams <chris.adams@jollamobile.com>
-
Alan Alpert authored
Task-number: QTBUG-30808 Change-Id: I1930bd91a6c2089047ac7e7d74da2c977c522e07 Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com>
-
- 30 Apr, 2013 - 4 commits
-
-
Alan Alpert authored
warning C4510: 'QQmlPrivate::RegisterCompositeType' : default constructor could not be generated Task-number: QTBUG-30454 Change-Id: I16ec8995ac1df3c92353006473ca082c4ed4e5b7 Reviewed-by:
Josh Faust <jfaust@suitabletech.com> Reviewed-by:
Thiago Macieira <thiago.macieira@intel.com>
-
Albert Astals Cid authored
Change-Id: I92317d8f5a6d6f60160139f7486ffa8ec5985656 Reviewed-by:
Alan Alpert <aalpert@blackberry.com>
-
Liang Qi authored
Autotest is included. Change-Id: I0f8614b502f1e51cab5612fee283c929e078108b Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com> Reviewed-by:
Liang Qi <liang.qi@digia.com>
-
Paul Olav Tvete authored
On Android, Key_Back is used to change to the previous state in-app, as well as to exit the application. QTextControl does not react to the back button, so it should not accept the event. Task-number: QTBUG-30752 Change-Id: I010d36c93f14384b96fb0b2f0015c57a2a3d2497 Reviewed-by:
Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com> Reviewed-by:
Frederik Gladhorn <frederik.gladhorn@digia.com> Reviewed-by:
Alan Alpert <aalpert@blackberry.com>
-