aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'origin/5.12' into 5.13v5.13.0-alpha1Qt Forward Merge Bot2019-02-0713-33/+186
|\ | | | | | | Change-Id: I5209d833e171c795556c075e2a5f964b59b6df2e
| * Try to stabilize tst_qquickwindow::defaultSurfaceFormatUlf Hermann2019-02-061-2/+4
| | | | | | | | | | | | | | | | Apparently the OpenGL context is not guaranteed to be available right after showing the window. Wait for it to appear. Change-Id: Ie3acdb857d4e3a8c6c148c57916a49a58c93a835 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
| * Fix bug where QQMPH kept an exclusive grab when no buttons were pressedJan Arve Sæther2019-02-063-0/+111
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This happened if you moved the mouse while doing a multitouch operation. More specifically this caused the bug: 1. Open qtdeclarative/tests/manual/pointer/map.qml 2. Rotate the map with two fingers (Do not release fingers). 3. Move mouse (no buttons pressed). 4. Release both fingers. 5. Move mouse again (error: the draghandler has a grab and thus the map is dragged even if no buttons are down). This happened because if you moved the mouse while having two fingers down, Windows would generate a *mouse*move* event with Left button or Right button pressed (which wasn't the case on the physical device but it's probably because of a bug in how mouse events are synthesized from touch on Windows). This caused the QQuickMultiPointHandler to do a passive grab. Then, when releasing the fingers it would not send a mouse release event (just plain touch release events), so the QQuickMultiPointHandler would keep the passive grab it had. All subsequent mouse move events would then be dispatched to the QQuickMultiPointHandler where it would assume that the button was pressed until it got a release event (but button was never pressed so that wouldn't happen). Eventually it would perform an exclusive grab, and dragging was initiated. Change-Id: I42b3133c5fde93c7f92f1cb28705156a69f9ad1c Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
| * QQuickWindow: don't give exclusive grab to invisible or disabled ItemsShawn Rutledge2019-02-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | An Item might set itself invisible or disabled while handling a mouse press, as an alternative to rejecting the event. In earlier Qt versions (e.g. 5.6) it did not end up with a grab in such a case. Task-number: QTBUG-63271 Change-Id: I12f646e4217d773d396f380672420c85e6adcd52 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Mitch Curtis <mitch.curtis@qt.io> Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
| * QMLJS: Have ScanFunctions iterate over ArrayPattern nodesErik Verbruggen2019-02-052-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | Like Codegen, have ScanFunctions iterate over the elements in an ArrayPattern, instead of recursing over the tail of the element list. This prevents running out of (native) stack, or hitting the recursion check limiter. Change-Id: I8203af3119ad50f19000a215af42649d9bcb3784 Fixes: QTBUG-73425 Reviewed-by: Lars Knoll <lars.knoll@qt.io>
| * Improve error messageRainer Keller2019-02-043-3/+7
| | | | | | | | | | | | | | Show more datails about what actually went wrong. Change-Id: I418a4d1f433bd4d440fc34e9a4932a9ea010b174 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
| * Merge remote-tracking branch 'origin/5.12.1' into 5.12Liang Qi2019-02-013-27/+54
| |\ | | | | | | | | | | | | | | | | | | Conflicts: src/quick/handlers/qquickpinchhandler.cpp Change-Id: I1f3618ceb93049623d6bf3a208b037c33d9d1f0c
| | * Fix axis constraints API and documentation:v5.12.1Jan Arve Sæther2019-01-213-27/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This should have been done properly for 5.12. Since this API was introduced in 5.12.0, we simply hide the documentation for the old properties and make sure the properties we want to expose are documented: * Document the xAxis and yAxis properties. * Deprecate the {min,max}imum{X,Y} properties, and hide them in the documentation. Fixes: QTBUG-73137 Change-Id: Ic749bcfec63dc4772f193ccae2a2750c20cb63aa Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* | | Fix warning about deprecated QPainter::setMatrix in QSGSoftwareInternalImageNodeFriedemann Kleint2019-02-051-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace by QTransform, fixing: scenegraph/adaptations/software/qsgsoftwareinternalimagenode.cpp: In member function ‘void QSGSoftwareInternalImageNode::paint(QPainter*)’: scenegraph/adaptations/software/qsgsoftwareinternalimagenode.cpp:477:43: warning: ‘void QPainter::setMatrix(const QMatrix&, bool)’ is deprecated: Use setTransform() instead [-Wdeprecated-declarations] painter->setMatrix(transform, true); Change-Id: I6e4047ee9c1a49ea6e0a445c8de281e049823902 Reviewed-by: Christian Ehrlicher <ch.ehrlicher@gmx.de>
* | | Tools: Fix deprecation warnings about QProcess::finished(int)Friedemann Kleint2019-02-052-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use QProcess::finished(int, QProcess::ExitStatus) with QOverload, fixing: qmlpreviewapplication.cpp:151:86: warning: ‘void QProcess::finished(int)’ is deprecated: Use QProcess::finished(int, QProcess::ExitStatus) instead [-Wdeprecated-declarations] connect(m_process.data(), static_cast<void(QProcess::*)(int)>(&QProcess::finished), qmlprofilerapplication.cpp:475:83: warning: ‘void QProcess::finished(int)’ is deprecated: Use QProcess::finished(int, QProcess::ExitStatus) instead [-Wdeprecated-declarations] connect(m_process, static_cast<void(QProcess::*)(int)>(&QProcess::finished), Change-Id: I0eb09e398b2a3b307fdd67a3fe505b1bdd1078f8 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* | | Add Settings.sync methodPaolo Angelelli2019-02-012-0/+20
| | | | | | | | | | | | | | | | | | | | | This matches QSettings.sync Change-Id: Ife73e16c23e1b03f7539fac70ea0a71b76bd3aca Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* | | Merge remote-tracking branch 'origin/5.12' into 5.13Liang Qi2019-02-0112-30/+78
|\| | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/qml/compiler/qv4codegen.cpp Done-With: Erik Verbruggen <erik.verbruggen@qt.io> Change-Id: I3ae3d64317e4f3fccba6605f4c6da15479ca75e0
| * | doc: Two class members can not have the same nameRainer Keller2019-02-011-1/+1
| | | | | | | | | | | | | | | | | | | | | At least gcc complains about it. Change-Id: I122b0bab2c2fcea24814a83f005be1ad4686aa78 Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
| * | V4: Fix unwind handler reset after for-in loopErik Verbruggen2019-01-311-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Consider this JavaScript snippet: function f() { for (var i in []) {} } This generates the following bytecode sequence: 2 0: 14 00 09 MoveConst r3, C0 3: ec 00 00 DefineArray (function), 0 6: da 00 GetIterator 0 8: 18 08 StoreReg r2 10: c0 0f SetUnwindHandler 27 12: 50 04 Jump 18 14: 16 0a LoadReg r4 16: 18 07 StoreReg r1 3 18: 16 08 LoadReg r2 20: dc 0a 09 IteratorNext r4, r3 23: 54 f5 JumpFalse 14 25: 50 03 Jump 30 27: c0 00 SetUnwindHandler <null> 29: c2 UnwindDispatch 4 30: 0e LoadUndefined 31: 02 Ret The problem is a normal loop exit: instruction 23 will not jump back, but fall through, and then instruction 25 will jump over the instructions resetting the unwind handler (27 + 29). Removing this jump fixes the issue. Change-Id: Ic9f03555ebebc27144490bce04e9a4166ed7c97c Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
| * | TapHander: do not "want" an eventPoint that is outside parent boundsShawn Rutledge2019-01-303-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | So far it was checking parentContains() on press, release, or when the gesturePolicy is WithinBounds, but not for each movement when the policy is DragThreshold (the default). This might explain most of the remaining warning noise: "pointId is missing from current event, but was neither canceled nor released" because it was possible for TapHandler to remember wanting a point that it should not have wanted, but without taking any kind of grab, and then complaining when that point was no longer present. Since it did not grab, it did not get the release, unless the release was part of an event containing a point that it DID grab. Fixes: QTBUG-71887 Change-Id: I26ce62279574cf6b0150f24e486f224a604ac6b1 Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
| * | Remove revisions from Qt.labs.settings methods and propertiesPaolo Angelelli2019-01-304-13/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Qt.labs plugins should always have revision 1.0 until they graduate. However, keeping registration Qt.labs.location 1.1 to prevent source incompatibilities. Fixes: QTBUG-73239 Change-Id: I01c66c5d3054fb95df54988b7ce6535ccc65d3a6 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
| * | Correctly scope unwind handlers for try blocksLars Knoll2019-01-302-6/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make sure the unwind handler is always reset when leaving the try block. This exposes a couple of failures in the ECMAScript test suite that were before passing by pure luck. Task-number: QTBUG-72858 Change-Id: I014b1e37c2beff136ecd53a665a2f10933f7e12c Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Erik Verbruggen <erik.verbruggen@qt.io>
| * | TextInput: Stop leaking password values to process memoryIvan Čukić2019-01-292-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The contents of a deleted QString can still remain in memory and can be accessible by tools that read the raw process memory. The same problem appears when the QString reallocates -- the old buffer gets deleted, but its contents will remain in memory. This means that a TextInput that serves as a password input field can leak parts of the password while the user is entering it (due to reallocation) and the whole password when the TextInput instance is destroyed. With this patch, the contents of the m_text string member variable will be zeroed-out before the TextInput is destructed. This is done only in the cases when the TextInput serves as a password field. Also, this patch reserves the space for 30 characters for m_text when the TextInput is used for password input. This is enough to make sure no reallocation happens in majority of cases as barely anyone uses passwords longer than 30 characters. [ChangeLog][QtQuick][TextInput/security] When the TextInput is used for password input, preallocate a buffer for the string that stores the entered value and zero-out the string on TextInput destruction to avoid leaking sensitive data to process memory Change-Id: I8f1f307b1cfc25ad51f48bae8509a258042a2e7f Reviewed-by: Frederik Gladhorn <frederik.gladhorn@qt.io>
* | | V4: Move relative-to-absolute offset calculation to base classErik Verbruggen2019-01-313-11/+28
| | | | | | | | | | | | | | | | | | | | | Now other subclasses of the BytecodeHandler can also use the method. Change-Id: Ib1a19e5ef6beb6c62b6a0214a6658f57b7e74a1a Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* | | V4: Generate labels for backward jumpsErik Verbruggen2019-01-3113-544/+104
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When analyzing the bytecode from top-to-bottom in a single pass, we don't know when a jump back to previously seen code occurs. For example, in the baseline JIT we would already have generated code for some bytecode when we see a jump back (like at the end of a loop body), and we can't go back and insert a label to jump to. As JavaScript has no goto's, the only backward jumps are at the end of loops, so there are very few cases where we need to actually generate labels. This was previously handled by analyzing the bytecode twice: once to collect all jump targets, and then second pass over the bytecode to do the actual JITting (which would use the jump targets to insert labels). We can now do that with one single pass. So the trade-off is to store 4 bytes more per function plus 4 bytes for each loop, instead of having to analyze all functions only to find where all jumps are each time that function is JITted. Change-Id: I3abfcb69f65851a397dbd4a9762ea5e9e57495f6 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* | | QQuickTableView: use QMap instead of a QRect to keep track of loaded columnsRichard Moe Gustavsen2019-01-303-162/+201
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TableView keeps track of which rows and columns that are loaded at any point by using a QRect called "loadedTable". loadedTable basically describes the top-left and bottom-right corner of the table that has been loaded (which also is what ends up visible on screen). But now that we prepare for making it possible to hide rows and columns, using just a QRect becomes to simple. A rectangle will only tell what the edges of the table are, but not if any of the rows and columns in-between are hidden and therefore not loaded. So a QRect(0, 0, 10, 10) will give us the impression that we have 10 visible columns on screen, but in reality, we might have a lot less. This patch will change this to instead use two QMaps to record loaded rows and columns. This will make it much more easy to deal with hidden rows and columns in upcoming patches. We use a QMap instead of a QHash/QSet to keep the list of columns and rows sorted, since we frequently still need to know the edges of the table, like before. Change-Id: I45736485c67042403b095e73b5f2effa411281d0 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
* | | Merge remote-tracking branch 'origin/5.12' into devLiang Qi2019-01-2962-269/+60242
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/3rdparty/masm/yarr/YarrJIT.cpp src/qml/compiler/qv4instr_moth.cpp src/quick/handlers/qquicksinglepointhandler_p.h src/quick/handlers/qquicktaphandler.cpp src/quick/items/context2d/qquickcontext2d.cpp Done-With: Ulf Hermann <ulf.hermann@qt.io> Change-Id: I109453131f9f0a05316ae37c7d6ed1edc8c0f9d4
| * | Fix byte code register dump outputSimon Hausmann2019-01-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The first register allocated in bindings is typically the return address register, which was erroneously shown as argument 0 instead of register 0. Change-Id: I00add0b5b1cd08a4c9b1d42ffe79d2ea7e5a73cf Reviewed-by: Lars Knoll <lars.knoll@qt.io>
| * | PinchHandler: fix pedantic warningsShawn Rutledge2019-01-282-20/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | - qreal<->float conversions are explicit - use qFuzzyCompare rather than == - remove padding between variables (but the class still needs padding) Change-Id: I9a9eb01f5a4108592b34e4b2f018c720ba19beb0 Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
| * | PinchHandler: Avoid unwanted translations when axes are disabledShawn Rutledge2019-01-283-7/+93
| | | | | | | | | | | | | | | | | | Fixes: QTBUG-72822 Change-Id: I2773ba14fcb24a47fe2ec04860b4aa305a051453 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
| * | Add *.pro.user.* to .gitignoreMitch Curtis2019-01-281-0/+2
| | | | | | | | | | | | | | | | | | | | | To ignore likes like foo.pro.user.4.8-pre1 Change-Id: If00bc540da49a06aa2be8ec38bc900996c6837c0 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
| * | Bring behavior of String.replace() in line with other enginesLars Knoll2019-01-252-14/+84
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "x".replace("x", "$1") gives "$1" in both JSC and V8, as there are no captures that could be used as a replacement for $1. Implement the same behavior as it's the most logical thing to do (even though it's undefined according to the spec). Two digit captures ($nm) work in a way that they get applied if $nm captures exist. If there are less than nm but more than n captures available $n is replaced by the n'th capture and m is copied over verbatim. Change-Id: I8b5f576f2c42c8334859ab7854dcdf07104dd35b Fixes: QTBUG-73152 Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
| * | Silent -Wdouble-promotion warningJesus Fernandez2019-01-251-2/+2
| | | | | | | | | | | | | | | | | | Change-Id: I44ba34365818adf6b9af022e4bf4ae9e02c3511a Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io> Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
| * | Canvas: Guard context pointer against external deletionUlf Hermann2019-01-233-145/+254
| | | | | | | | | | | | | | | | | | | | | | | | | | | You cannot keep the context when reparenting the canvas item. Use a QPointer prevent dangling. Task-number: QTBUG-73113 Change-Id: Ie7021c6f0bb0d09923eb358dc7e51d6727e74a7a Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
| * | MemoryManager: Only clear weak values onceUlf Hermann2019-01-235-5/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We want to keep the weak values alive while the destruction callbacks are running, so that they can still access them. We set them to undefined later anyway because we expect the destruction callbacks to mess with the values. Therefore there is no point in also setting them in between. Fixes: QTBUG-72137 Change-Id: I83f70230f5b4ad2761c74770f975b14a5ca71f18 Reviewed-by: Lars Knoll <lars.knoll@qt.io>
| * | QQmlNotifier: Always keep the isNotifying flag when updating senderPtrUlf Hermann2019-01-234-20/+94
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the sender gets deleted we still want to retain the flag that tells us that the notifier is currently active. Otherwise we can miss the error message about synchronously deleting objects while signal handlers are in progress. Task-number: QTBUG-73013 Change-Id: I8abba9b492327c15963d1875841c6822f345a89e Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
| * | Add handlers declared as Flickable children to its contentItemShawn Rutledge2019-01-2214-5/+751
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | QQuickItemPrivate::data_append() was not invoked when any kind of Pointer Handler was directly declared in a Flickable (or subclass) because QQuickFlickable redefines the default property to be its own flickableData property. So we need to repeat the special handling in QQuickFlickablePrivate::data_append() too. The handler must be added to the private->extra->pointerHandlers vector, so that QQuickItemPrivate::handlePointerEvent() will attempt to deliver events to those handlers. TapHandler seems OK (especially with its default gesturePolicy so that it does not do an exclusive grab). PointHandler seems OK. DragHandler competes with Flickable for the exclusive grab. pressDelay can help; or set acceptedDevices: PointerDevice.Mouse to allow the mouse to drag but not flick, and the touchscreen to flick but not drag. Fixes: QTBUG-71918 Fixes: QTBUG-73035 Change-Id: Icb97ed5230abe0cb6ec0230b5b5759a0528df7e8 Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
| * | Skip shadersource-dynamic-shadersource test on XCB platformUlf Hermann2019-01-222-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test crashes, which is counted as failure, even if the test is blacklisted. It also doesn't only crash on Ubuntu 18.04 but also on Redhat 7.4 and Ubuntu 16.04. Just blacklist it for any linux for now. Task-number: QTBUG-69893 Change-Id: Icc4c41b5d6fa339075b569fcd53220692e882d23 Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
| * | TestLib: Remove outdated note from TestCase.mouseDragJoerg Bornemann2019-01-221-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The docs of TestCase::mouseDrag say "Note: this method does not imply a drop action, to make a drop, an additional mouseRelease(item, x + dx, y + dy) is needed." However, you can find that exact line at the end of the function. This commit removes this note and amends 73131271. Change-Id: I601ed441e23e9ed66a08fd0f1d23ff5bbb5bc091 Fixes: QTBUG-72954 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
| * | Merge "Merge remote-tracking branch 'origin/5.12.1' into 5.12" into ↵Liang Qi2019-01-2226-49/+58845
| |\ \ | | | | | | | | | | | | refs/staging/5.12
| | * | Merge remote-tracking branch 'origin/5.12.1' into 5.12Qt Forward Merge Bot2019-01-2126-49/+58845
| | |\| | | | | | | | | | | | | Change-Id: I1e0bbc35807bd0f7f96694539d2fbec0f83ddb16
| | | * Fix cacheFlush ManageCaches flags for INTEGRITYJanne Koskinen2019-01-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use ACCESS_DST_SYNC to flush I-cache instead of ACCESS_DST_COHERENT D-cache flush. Fixes invalid instruction crash caused by out of sync instruction cache. Task-number: QTBUG-72267 Change-Id: Icb95050c9fee42ae7fa659b8ed4d3a4fbb98df6e Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> Reviewed-by: Timo Aarnipuro <timo.aarnipuro@qt.io>
| | | * V4: Fix stack alignment in JITted codeErik Verbruggen2019-01-152-13/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Helper calls done for to-integer and to-number conversions did not align the stack on 16byte boundaries, which could lead to crashes if somewhere in that call a vector instruction is used that expects such alignment. Task-number: QTBUG-71325 Change-Id: Ieec05a93a1f69b538e6c8930b8eb64cbe85c35d4 Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io> Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> (cherry picked from commit 3795904e3831722e222fa32a1e52aeb6b3e6ba87) Reviewed-by: Lars Knoll <lars.knoll@qt.io>
| | | * Add changes file for Qt 5.12.1Antti Kokko2019-01-151-0/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + 5bf057eca49b59f7516c6d5bb3f4dbbeb4713942 Doc: Remove wrong return type + 31a9acd0348750e60feda9bdee07afc7511a6be7 Also store the raw string value for template strings in the lexer + 4241ce2cfc624ae51ac911c11d065fc703dfadc5 Pass the raw string value to template literals + 9755cf48cbaa322ec918e0d70d54124e22f9c550 Create proper template objects + b340d8bb8886ecb46c8702127ff4dffb727c4f24 QV4::Scoped: Use explicit operator bool + f2244820016f27ac2f7d26c8ba51d806956e4968 DesignerSupport: Fix emitComponentCompleteSignalForAttachedProperty + 2cc77519ebf1b5e7249c1e2f6fec97816c068cd0 Remove misleading Q_UNUSED(uri) + 0fce92af2cab51d03f33230718ab5ae35149b9e1 Correctly read files with a \0 in them + b1f07986c30978ed6636457e8d3f4a65c5db38a3 Create proper template objects for tagged templates + 52e326cf177c23147146d9e1de2de920f62ddbc9 Doc: Add enumeration object attributes to the QML Reference + 919a6804990277fb0eb10015559fd4a6e9b26547 Doc: Add a link from enumeration basic type to enum attributes + 900786226404c915f3b2eb2840a1f3eb391db69b Doc: improve qmlRegisterInterface() documentation + 1d024222d8d57ffa03050a177409be6a8ebb73e1 QUICK_TEST_MAIN_WITH_SETUP: improve documentation + 74a5ce02667ceefe31aba9a23246b9c512527014 Fix TestCase::skip to ignore rest of the data rows in TestCase + 6c08137faf1a53db879701126608833474a2450b Fix null pointer access in QQuickOpenGLShaderEffectMaterialCache + 7eaa93680ce583354f23f3b29bd6db59169dfece Bump version + 4651aecaee320b74b6ffcb6fe34fc3d43726010e Fix more null pointer accesses in QQuickOpenGLShaderEffectMaterialCache + dcf41b5f69d0e199d0a6a8faaad981f73e1c9aa0 Yarr: Fix developer build with MinGW 64 + 8af9d69554065924f9c92b29dd09d08ba6650328 QML Tooling: Fix ordering of memory events in V4 profiler adapter + 064f0d3d23097cb181166c3e966287490773f23c Fix leaking textures and animation resources by software backend + e746e55f2451a800744ccfcbc9f83fdc3a16337c Fix leaking resources by OpenVG scene graph backend + 1613e32042a8e710c3105b926422827ccaad1c5c qmlpreview: Fix typo + 80d26c15080c92012f0a51f7675d3c70ad56a8bd qmlpreview: Use a better file system watcher + 89a1d4ff3f829635d80a90112f6b2d44cc274b1b masm: Don't call fclose(nullptr) and initialize statics + 9b7b26ca50b0700aea9e756551dfec1cf098f4cd Doc: Use \section1 to clearly identify the different parts + e12dc7910aaeb6e71275115c30a0eb227ac3b403 macOS: Remove blacklist entries for no longer supported OS versions + 16e3859af180b28157f39ad5d1f77ff3571753a2 Qt Quick Test: support tags filter on tests run + e668e12c58c489bda79cc3c116719369cdb06650 QML Inspector: Use Qt5-style connection + 0647853c1659515684da1fb0f44d12eac993dc69 Qml Tooling: Fix crash in QQmlProfilerService test + 71645c45b9880d1a349c9a41a73d455f31c9de75 Qml Tooling: Correctly sort debug messages into traces + 87265c7ab8743ece92262cd6b79bbba9dddd1fe1 Qml Tooling: Test that trace events arrive in chronological order + a7948a7519c3b0d4660637e8697311bd8abdc85d Properly mark variables as unresolved when accessed from eval + f92c48a231d5f98513e649340652baaf01f327ad JS: Check array subscripts for validity when generating code + 0d3eccd2a982faa46e8515cd5c55f95adcc5f868 Stop codegen after error + 435cbb65ef6280f7b8417cb03754765f8289419d Fix tiling overflow with BorderImage + 75937c9da7910ce41b4b3207d66d844ed9624df8 Fix signed/unsigned warning in VS 2017 + 3e9b752bf4114b2b06e2f8f65aad67606dfc0215 QML: Use all available type information to find enum types + 9d319e20cd76d25332d4aefcf92d6f174b910d51 JS: Handle check for dangling jump gracefully + a54e15bc7968a546fc939fc2d166261fd6513d5a JS: Check pattern target to be an lvalue + 2b52a997ce3679ac4c94b7c117b0ea11c1523b60 QML TypeLoader: Sort composite singletons before recursing into them + e3c0bb7811407bad1f65ea55639a4b1d1d39be15 Add changes file for Qt 5.11.3 + 9a7c5a925c4d62f4fe23d31b1f8636d415b6307c Doc: Fix spelling of qjsvalue_cast() + 63ada5fa00ba37e0fbfcd7b70dcbd99580dd7c4f QQuickText: Signal content height/width changes also when resetting + 6b3365b2ea3b445cae2cf657392176bff19a0fe4 Use msvc qmake scope where appropriate + 560a1991ac4524ff16352da23a2b54d717548f33 Fix updating of text nodes in QQuickTextEdit + 03f492f91a9ac6d33be05488f7ea6fb5decaf873 Fix vertical alignment of images in a text document + 33c13efd91954fb50019e82f3ab8e8e1d8458332 Ensure our builtin constructors are subclassable + 9926a4a49e8211a996667b467fd98b915e9f9d34 V4: Avoid copying WeakValues with wrapped QObjects + 52e4e125b6d71baeb843da740cecf319fee99511 qmlscene: Fix potential invalid memory access to QTranslator + 900d2f611475df6e43972eac5fc3c9b4b06b1c0e Improve documentation of QML's handling of dates and times + 5246b910771e0dd824b4eea7c5245e5f9f3a63f0 Fix qmlplugindump version dump issue + ba9d630c3de6a47d96e41b5a4b10ce2d5861e1fb Fix Qt Quick Compiler with CMake on Windows + 4eadcd6ebaec5a172b874bbb28efe06f3b473817 QSGSoftwareInternalRectangleNode: Reduce memory allocations + d958f830e8b5b27e88a7fe9d14aa61d832a6756c QSGSoftwareInternalRectangleNode: Remove unnecessary loop iterations + e1a0e894aa09dd1323a7792192f1d68ee6677f8a QQuickTableView: connect directly to the model, and not to the QPointer + 0e87966c8f815269b770a0a31974e0cd5b8ab26e Fix failing assertion in memory pool allocator in large QML scenes + 04af30c91a68a04ab1830d6ddc1bf470354b1862 Disable antialiased clipping when painting images + e7d19a2a0fcbec38b7e132634d0ebe79b772c61b Fix stale QML cache files when using assets:// on Android + 597ce09c7a1d8b89e9473faae900321ef2d4181d JS: Limit expression and statement nesting level + 2fa1c92cb7e60f89e200eff48cf7e76d8d2febe6 Fix parsing of js files via Qt.include() + d0a52c72b5756787ceb6094117cd71d935badc06 Prevent overly drawn-out animation when snapping + b17091b0006e41c0bb4ddf77dbbc09621d809aea QML: Also clear outerContext's contextObject on destruction + ea725e1b54e5a28fb7c37f23acfdd95e6269624a Declare the enum so it can be passed to the QML side + 3a025d75fd470dfcda5ae67e5b8ece0b00cdc8c9 Fix line number reporting in scripts when lookups are enabled + b55b3692f6cc57f8a7ef972388504b5133331ceb Fix compilation with gcc 4.8 + 9d2a929fa4dd0beae3c30fb08d4ed4df7368ea4f tst_qquickwidget::enterLeave(): Handle varying screen setups + 1cd3b2acfeb041ef54fe546b07a5e9efb5a2099b Fix an ambiguity with gcc 4.9 + ee2ac69595d3f854f7bf7158e600091f2675fa18 Add dynamically-created Event Handlers to the relevant handlers vector + be3772725cec64e533d35a38376077363af01ede Ensure that each Event Handler has an Item parent rather than asserting + f8f0f0835a971a658f4ee2ae386e448338b1a7d7 TapHandler: ignore scroll events and native gestures + 0b586e5b504f66c5ba2b690eda1c89e3e5dfdca3 Doc: fix QUICK_TEST_MAIN_WITH_SETUP function table + 60cb95508c5dac036663dfcaa2c60e884b5dcad9 Doc: Restore QtQuick.Shapes documentation + c352ca4a3dc2e6e3a4c039589849cf502911ba95 Fix missing strike out + b1494ffa7d0c9bfa68019a3fc4969f9124d4889c Fix typo in notify signal emission + e3446c8225acbaa6a613d6c62e8e2fc58e2b70b0 Add qmllint in android builds as well + 1d88e9919ff837d535f9bbde53613b6a6b96fcd8 QML: Fix registering and unregistering of context objects + e7eae05a3c45b239b5510cb566947c2334749b56 Avoid memory leaks in QQmlComponent test + cb5e61c5f0b912c798791adcc3a35e6083294782 Fix ICC warning about old-style scoping rules + cf5da3e8e235331c4929f236a1966bbd0cf28256 Fix ICC change-of-sign warnings + 1b79a40466ccb1ba52b596c69f3af607a1148b07 Doc: velocity properties must be set to -1 when setting duration + 358a72b6ecd0fef69edf5355f299af10225a6c8b PointHandler: distribute simultaneous touch presses properly + 48eb8da7f4bde39e2f9d1a6eef4978d11bf67ca1 nothread: do not delete reader thread object before it gets used + 12f89fb8dda86c61277e3814912013873b1657e6 TapHandler: clean up when wantsEventPoint returns false + f922ac81cfb9a405e24e7335b44698a6210a5fb4 Un-blacklist tst_touchmouse::hoverEnabled + e12e36f802759d61c02c94ee6432e79745dce59b Un-blacklist qsequentialanimationgroupjob test + aad66998c379deba70aceda27c09d4680bbf10ff qmlscene: Make it explicit that QCA::installTranslator is static + c401ae278b4bb91c70c6d7df974a241d7c68855b QML: When destroying a context, clear any pointers to it + eb1f9c2e687002643ebc80e51d4bfc5f0258da0d CMake: Don't handle empty resource files + d6e560c356791d516856c38566104fbb2bb6c730 When there are no points to grab, then we should return false + 3124b03276398f68dd8f3afe18866cfb6ec8a035 stabilize and standardize tst_qquickwidget + bffc040f8014b361992cd92671e559c1c2abd633 Tests: Un-crash image comparison tests + d462cdb4201a9b02b57488a8e7029088d4807895 Add binary compatibility files for 5.12 for QtDeclarative + 75ebbd0b354739150e10da7216b44e2dde2c2b14 Quote stringified generic variants on JSON.stringify + c57681bc376d1d912d23b044c48932fa8f7816d7 qquickpixmapcache: Fix invalidation of m_cache while iterating it + 0e33ba51166dd68a26c56d85a1155c4849d59e4a Doc: Fix link issues + c327c43be82c6a2827df1f493ca4e3487a0fc9c3 Tests: Don't capture stack value by reference + 5ed082ea4ce3580134a9a0c83e6fdb81a6231c8e Bump version + 5208b2a671010b11b78312f9c4fe3c3098d253b4 Fix regression in border-top with high-dpi Change-Id: I61405501951a112cf7e5a63166e89dbe521ca1e5 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> Reviewed-by: Andy Nichols <andy.nichols@qt.io> Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
| | | * When matching RegExps catch JIT failuresUlf Hermann2019-01-096-24/+114
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Yarr JIT can generate code that fails to evaluate the RegExp at runtime. In that case we need to fall back to the interpreter. Also, don't needlessly cast the unsigned return value of RegExp::match to signed int before range-checking it. And fix some typos in the comments for the disassembler dumps. Fixes: QTBUG-72879 Change-Id: Ic8f80c076d6461d714816a9f66e1cac1d9b0c7a8 Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
| | | * Merge 5.12 into 5.12.1Kari Oikarinen2019-01-0861-192/+501
| | | |\ | | | | | | | | | | | | | | | Change-Id: Ic746fbce93430867e2eda4bc7155d34e20a4aa2b
| | | * | Fix regression in border-top with high-dpiAllan Sandfeld Jensen2019-01-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Device pixel ratio was included twice. Task-number: QTBUG-72603 Change-Id: Idd1b75c3b1926a6381bf258c1b705be10c5575b9 Reviewed-by: Frederik Gladhorn <frederik.gladhorn@qt.io>
| | | * | Add binary compatibility files for 5.12 for QtDeclarativeMilla Pohjanheimo2018-12-204-0/+58401
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Binary compatibility files added. Change-Id: I98e3a26f0f5883217c05dfe35e723bee4f1521f8 Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
| | | * | CMake: Don't handle empty resource filesAndy Shaw2018-12-173-11/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [ChangeLog][Qml] Empty resource files will not be passed to Qt Quick Compiler to be handled when using CMake. Change-Id: I1513d29b70d8a4b08a2947f4a97fbd525c5ace8f Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
| | | * | TapHandler: clean up when wantsEventPoint returns falseShawn Rutledge2018-12-134-2/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We already emitted grabCanceled() to inform QML callbacks, but we didn't call reset(). It seems more proper to do everything that would normally be done when grab is canceled. TapHandler should not give up its passive grab yet though, because that prevents delivery to any parent Flickable that might be filtering events. A parent Flickable should be able to start flicking after the drag threshold is exceeded (it happens to be exactly when TapHandler gives up). Fixes: QTBUG-71466 Fixes: QTBUG-71970 Change-Id: Ibba1b0de92cfd88547eeb44edb095d019de76a94 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
| | | * | PointHandler: distribute simultaneous touch presses properlyShawn Rutledge2018-12-133-1/+166
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If multiple touchpoints are pressed simultaneously, each point can be grabbed by one PointHandler instance. Each PointHandler instance cannot grab more than one point, nor grab a point that is already chosen by another PointHandler. This was always the intention, but got broken (perhaps by 3523b676382db4aa39adeb9126d8bb2185e84403), and there was no test coverage of this case until now. Fixes: QTBUG-71431 Change-Id: I6d7614eb4767c677d929291f917cf62d9c03bd93 Reviewed-by: Andre de la Rocha <andre.rocha@qt.io>
| | | * | Fix typo in notify signal emissionRobert Griebl2018-12-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Change-Id: Ic2c298d14eb85ee8702eb751dd269eb0e3e11cc6 Reviewed-by: Michael Brasser <michael.brasser@live.com>
| | | * | Doc: Restore QtQuick.Shapes documentationTopi Reinio2018-12-102-8/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sources for this module were recently moved. Add the new directory to documentation config to make the documentation generate again. Also, make the documented QML module version track the minor version of Qt. Change-Id: I56f439c141cbf39639a97d44d328c068fff6e96e Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* | | | | Tooling: Use fprintf rather than qDebug() for debug warningUlf Hermann2019-01-281-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This warning is generated from a statically called ctor. At that point the system facilities to run QMessageLogger may not be in place, yet. In addition, we actually don't want the message to go through the regular QMessageLogger redirection and possibly filtering. The message should always be shown. Change-Id: Ia89822b26e04591fe309581c3c84a4c7e54759a6 Fixes: QTBUG-73217 Reviewed-by: Andy Shaw <andy.shaw@qt.io> Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
* | | | | V4: Collect trace information in the interpreterErik Verbruggen2019-01-2529-208/+953
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Collect type information about values used in a function. These include all parameters, and the results of many bytecode instructions. For array loads/stores, it also tracks if the access is in-bounds of a SimpleArrayData. Collection is only enabled when the qml-tracing feature is turned on while configuring. In subsequent patches this is used to generated optimized JITted code. Change-Id: I63985c334c3fdc55fca7fb4addfe3e535989aac5 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-24 10:08:02 +0000